-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
ARN attributes for more AWS resources? #943
Comments
That would be really really cool. Tagged. |
Stumbling on to this... I added a I'm sure if that's a good starting point as something we can extract, but I thought I'd mention it here. With the change to awslabs/aws-sdk-go library from goamz, maybe this feature is easier to come by now? |
I would like to request this again as I ran into wanting the ELB arn for an IAM policy. |
I am going to close this out - we are adding ARNs on a resource by resource basis when the API returns them and also when people make specific requests :) Please feel free to open a PR for a specific ARN addition that you need :) Paul |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Floating an idea, which I'll try to implement:
Maybe more resources should have
arn
attributes. With IAM somewhat implemented (#939) it's likely these will be needed. For example, I have a process that registers instances with an ELB, and I need to create an IAM policy for that process, and to limit it to controlling the ELB it's responsible for, I need that ELB's ARN.While it's possible to construct the ARN from the
name
attribute if you also know the region and the account number, it's a real pain to pass these variables around. Especially the account number: I don't even have it in the manifests. I don't even really know it: I have to look it up. Even with all the information available it's easy to miss or double a colon or otherwise mess it up.Seems the providers could do this pretty easily, and make things more elegant overall.
The text was updated successfully, but these errors were encountered: