feat(cloudformation-template): allow to set a static prefix to stack exports #529
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Simple non-breaking change to the CloudFormation template to allow users to set a static prefix that will be used in Stack Exports rather than interpolating the stack name.
Motivation
When deploying the template using StackSets, the resulting stacks have random-ish unpredictable names.
This prevents users from relying on predictable Stack Exports to discover the Forwarder Function ARN or the Datadog API Key Secret.
Testing Guidelines
Tested the template with no parameters to ensure no changes.
Tested the template by deploying via StackSet with prefix setting.
Types of changes
Check all that apply