History

root c2201fb097 rnacher init		2024-10-14 05:21:48 +00:00
..
Dockerfile	rnacher init	2024-10-14 05:21:48 +00:00
Jenkinsfile	rnacher init	2024-10-14 05:21:48 +00:00
README.md	rnacher init	2024-10-14 05:21:48 +00:00
aws.yaml	rnacher init	2024-10-14 05:21:48 +00:00
azure.yaml	rnacher init	2024-10-14 05:21:48 +00:00
gcp.yaml	rnacher init	2024-10-14 05:21:48 +00:00
tag-to-save.yaml	rnacher init	2024-10-14 05:21:48 +00:00
untag-to-delete.yaml	rnacher init	2024-10-14 05:21:48 +00:00

README.md

QA Cloud Custodian

QA custodian will clean up resources in AWS, GCR, and AZURE. Currently, we have automation configured for:

AWS
- instances
- NLBs
- EKS
AZURE
- VMs
- AKS
GCP
- instances

Getting Started

New Hires - make a PR adding one line to the user-keys.txt file. Use that key in ALL resources you create when using SUSE resources. Keep it short (6 characters or less) unique to you, and recognizable by others (And, this is case sensitive!). For example, if your name was Jane Elaine Morrison, something like jem would suffice. Just make sure you can remember it, and others can know who's it is if they are on your team.

About the Code

This suite is fairly simple, and runs using Cloud Custodian. Our modifications consist of the following:

text files
- *-keys.txt representing special keys that correspond with QA's resources
- regions.txt (AWS explicit) representing the regions we use on a regular basis, and therefore what the custodian will check against
.yaml files, which are different configurations for the custodian to use when running.