-
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
dynamic referencing in a template not resolving #30
Comments
Hi @hine0088 I assume you're referring to CloudFormation dynamic references, for example: Both CloudFormation dynamic references and Jinja use the same special characters During the Jinja compilation phase of the Proton deployment, Jinja is attempting to interpret that dynamic reference because it is between You can use Jinja escaping to escape those characters so that they end up in the final CloudFormation template: For example:
Or:
|
That worked perfectly, thanks so much! Easier to see with hindsight now. I did the following MyRDSInstance: |
I'm going to resolve this as it seems to have been cleared (thanks Clare!). We are looking to compile some best practices when writing a template, and will add this suggestion |
While using dynamic referencing in a template, it seems that the secret value isn't resolved correctly and results in an empty string. The file uploaded to S3 while creating the environment template has the correct syntax but the template as seen in the CloudFormation console for the stack seems to have an empty string. Instead of letting CloudFormation resolve the dynamic references, it seems that it is being resolved even before it gets to CloudFormation. Interestingly enough, it is taking the dynamic referencing syntax out of the comments as well which leads me to believe that it is parsing the template entirely before creating the CloudFormation stack.
The text was updated successfully, but these errors were encountered: