fix: ensure unique names for infrastructure resources #8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
raksiv
force-pushed
the
NIT-379
branch
3 times, most recently
from
6061f52 to
2a8b8b0
Compare
resources updated - fargate, lambda, loadbalancer, vpc, cloudfront, security group relies on - nitrictech/suga#103 which injects the stack_id
Member
Author
|
Updating platform to accept unique variable names. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Resources updated to include stack_id in name - fargate, lambda, loadbalancer, vpc
Relies on - nitrictech/suga#103 which injects the stack_id for infra resources