Skip to content

Conversation

@acanbym
Copy link
Contributor

@acanbym acanbym commented May 14, 2025

This PR updates the playbook in order to make it a bit clearer regarding tagging.

@acanbym acanbym requested review from a team as code owners May 14, 2025 09:16

- `Application`: The full name of the application or service. This should match the name used in the Service Catalogue, e.g. `Repairs Hub`, `Common Fate`.
- `TeamEmail`: The email address of the team responsible for the operation of the service. Must be a valid email group, not an individual.
- `Environment`: The name of the environment, must be one of `dev`, `stg`, `prod` or `mgmt`[^environment-tags-source].
Copy link

Choose a reason for hiding this comment

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

just a little comment here, we've added "pre-prod" to the tag policy.

Copy link
Contributor

@Duslerke Duslerke left a comment

Choose a reason for hiding this comment

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

Backup policy being capitalised while environment not causes a little bit of confusion.

@acanbym acanbym merged commit a05d993 into main May 14, 2025
4 checks passed
@acanbym acanbym deleted the feature/update-tagging-standards-and-how-to branch May 14, 2025 10:07
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.

5 participants