You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new function, possibly called !Link could remove this friction in a lot of cases:
The expected input is documented and hopefully in the schema
The possible output is documented and hopefully in the schema
For the case where there is a 1-to-1 mapping CloudFormation should be able to figure out which attribute is needed and resolve it. For other cases there could be:
a push to improve outputs (adding more variations to !GetAtt so they can be !Link'ed directly in the related resource without the user having to use !Sub to construct an Arn)
a way to specify a template in the schema at the resource property level (This input should be of resource type AWS::Foo::Bar and use this !Sub to construct the value)
an independent mapping that defines these relations explicitly.
The text was updated successfully, but these errors were encountered:
benbridts
changed the title
Add a !Link (or equivalent function)
Add a !Link (or equivalent) function
Aug 26, 2020
@benbridts 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.
lejiati
transferred this issue from aws-cloudformation/cloudformation-coverage-roadmap
May 10, 2022
A lot of time writing CloudFormation is spent by looking up expected inputs and outputs. With questions like:
A new function, possibly called !Link could remove this friction in a lot of cases:
For the case where there is a 1-to-1 mapping CloudFormation should be able to figure out which attribute is needed and resolve it. For other cases there could be:
The text was updated successfully, but these errors were encountered: