Skip to content

ENG-1345 selection_tag docs#130

Open
terado wants to merge 3 commits into
mainfrom
nimi11-eng-1345-selection-tag
Open

ENG-1345 selection_tag docs#130
terado wants to merge 3 commits into
mainfrom
nimi11-eng-1345-selection-tag

Conversation

@terado

@terado terado commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Description

selection_tag documentation changes

Comment thread README.md Outdated
Co-authored-by: hirra-farooq <85997380+hirra-farooq@users.noreply.github.com>
Comment thread README.md
For **non-production** environments, you have flexibility:

- Use the same tag (`NHSE-Enable-Backup` = `True`) if you are going to create a single backup plan in the account.
- Use a different tag value (e.g. `NHSE-Enable-Backup` = `dev`) or a different tag key entirely (e.g. `BackupDev` = `True`) if you need to distinguish which resources belong to which environment's backup plan.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Use a different tag value (e.g. `NHSE-Enable-Backup` = `dev`) or a different tag key entirely (e.g. `BackupDev` = `True`) if you need to distinguish which resources belong to which environment's backup plan.
- Use a different tag values (e.g. `NHSE-Enable-Backup` = `dev`) or a different tag keys entirely (e.g. `BackupDev` = `True`) if you will have multiple backup plans in the account and need to distinguish which resources belong to which backup plan.

# Use any tag key that suits your project. For production, we recommend "NHSE-Enable-Backup".
# For multi-environment accounts, use a distinct tag per environment to avoid plan collisions.
# See the Tagging Strategy section in the root README for full guidance.
"selection_tag" : "NHSE-Enable-Backup"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After speaking to Susana as well i think we should remove "selection_tags" section from the example to deter people from further using it. and potentially leave a comment saying further information and possible extensions of section_tags can be found in # See the Tagging Strategy section in the root README for full guidance.

@hirra-farooq

Copy link
Copy Markdown
Contributor

Comment from Susana - also update the readme / any where else that we users of this blueprint should not copy this blueprint into their own repos but should use as a terraform module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants