Making scc-notification ID randomizable org-level to allow deploying multiple TEF instances same org #385
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.
There are 2 org-level resources with hardcoded IDs - tags and SCC notifications
For tags name randomization support already available - just put in 1-org/envs/shared/terraform.mod.tfvars create_unique_tag_key = true (default)
Similar mechanism for SCC notifications - enable uniqueness via randomization by setting create_unique_scc_notification = true in the same file