Skip to content

Adds gu:tool and gu:application-repo definitions to AWS tags glossary #184

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
SHession wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Adds gu:tool and gu:application-repo definitions to AWS tags glossary #184

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions AWS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,9 @@
* `CODE` for pre-production
* `INFRA` for infrastructure or singleton resources e.g. [elasticsearch-node-rotation](https://github.com/guardian/elasticsearch-node-rotation)
* `App` - the individual service e.g. `image-loader`
* `gu:tool` - the tool which the resource belongs to, similar to stack but more specific e.g. Composer, Workflow, Grid
* `gu:repo` - the GitHub repository where the resource's definition can be found
* `gu:application-repo` - the GitHub repository where the application code can be found
* If a resource needs to be shared across multiple environments, prefer to define it in it's own CFN template as the same resource cannot be defined in multiple templates
* Prefer continuous delivery of infrastructure via Riff-Raff over manual deployment
* This provides a better audit trail
Expand Down