We use the
gl_ prefix for all labels and tags. All keys use underscores (
snake_case). All values should use hyphens (
alpha-dash for slug'd values), however underscores are allowed.
See the list of global labels and tags that should be applied to each resource.
||Required||Shutdown After Days||Usage Documentation|
||Optional||Shutdown Outside Working Hours||Usage Documentation|
||Auto Calculated||Shutdown Date||Usage Documentation|
This label/tag is required. Some Terraform modules will automatically calculate this for you.
The value set is used to calculate the
gl_sandbox_shutdown_date. Our sandbox automation scripts will handle the shutdown of compute and other resources for you.
Our scripts will rescan shutdown resources and permanently destroy them after 90 days if they have not been powered up since the scripts powered them down.
||(default) The default for all environments unless overridden.|
||This is the recommended range for longer-term test environments.|
||The range of accepted integer values that do not require infra/security review unless a vulnerability is detected.|
||These values can be used but an infra/security review will be performed.|
||This is the recommended value for perpetual environments that do not power off. All environments with a
This label/tag is recommended. Some Terraform modules will automatically calculate this for you. This is for future proofing and may not be fully implemented in this iteration.
||(default) Resources can be systematically powered down overnight between 6pm (18:00) and 6am (06:00) and on weekends during the environment owner's timezone as set in
||All resources will run 24/7 without any disruption. This consumes 720 compute hours per month.|
This label/tag is optional. Some Terraform modules will automatically calculate this for you.
The expiration time is calculated as 23:59:59 UTC on the date calculated from the
gl_sandbox_shutdown_after_days value and the timestamp the resources was initially provisioned in the cloud provider. Due to limitations with the allowed characters in labels, we do not include the time since it requires colons and plus symbols for timezones.
This value can be updated/extended systematically as part of our expiration scripts (and future Slack notifications) if a user needs more time. After the expiration date has passed, an automated
terraform destroy CI pipeline will run to remove all resources in the environment.