Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--integration-arn doesn't work if the role is on different path #201

Open
americanstone opened this issue Jan 31, 2022 · 0 comments
Open
Labels
bug Something isn't working

Comments

@americanstone
Copy link

americanstone commented Jan 31, 2022

Description

when pass the integration-arn parameter if the arn has certainn path. the cli fails
e.g.
arn:aws:iam::xxxxxxx:policy/acct-managed/new-relic-lambda-cli

Steps to Reproduce

--integration-arn arn:aws:iam::xxxxxxxx:role/acct-managed/NewRelicInfrastructure-Integrations

I believe this line of code in utils.py

external_id = parse_arn(role_arn)["account"] result["resourcetype"], result["resource"] = elements[5].split("/")

throw error

Expected Behaviour

don't parser the external_id from role arn, allow it pass via cli parameter

Relevant Logs / Console output

Your Environment

  • ex: Browser name and version:
  • ex: Operating System and version:

Additional context

@americanstone americanstone added the bug Something isn't working label Jan 31, 2022
@americanstone americanstone changed the title --integration-arn doesn't work if the role is on different path --integration-arn doesn't work if the role is on different path [dup] Jan 31, 2022
@americanstone americanstone changed the title --integration-arn doesn't work if the role is on different path [dup] --integration-arn doesn't work if the role is on different path Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant