-
Notifications
You must be signed in to change notification settings - Fork 13
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
Intrinsic function for constructing ARNs #56
Comments
@benkehoe Thank you very much for your feedback! Since this repository is focused on resource coverage, I'm transferring this issue over to a new GitHub repository dedicated to CloudFormation template language issues. |
I would recommend the function contains an action verb as well, such as When I first read the issue title, I thought this was going to fix the pain of knowing when I need to use So, for ease of disambiguation of intent, let's always prefix functions with verbs. |
That's a good point, I've changed the title. |
ARNs are a pain to create. They aren't always provided (see aws-cloudformation/cloudformation-coverage-roadmap#68), and they all have slightly different formats. We should have a function that assembles ARNs for us. I imagine a syntax like:
Resource
can be a string or a list, which will getFn::Join
'd by the empty string. IfAccount
istrue
, it will use theAWS::AccountId
pseudoparameter, iffalse
, it will be omitted, and if it's a string, the value will be used. Similar forRegion
.What I'd really like is for the user to not have to provide
Account
andRegion
for most ARNs. Make them optional, and know the rules. CloudFormation should know that S3 buckets don't have accounts or regions. It's not that hard to build such a thing. And if it's not 100% up to date, users can specify explicitly.The text was updated successfully, but these errors were encountered: