labels
devops-workflow/labels/null
Terraform module to create consistent naming for multiple names
 terraform-null-labels Terraform module to provide consistent label names and tags for resources. This is similar to label except: - This accepts a list of names, instead of a string. And returns lists. - This uses null-resource instead of locals. This was required to be able to use count. - Currently this does not return tags The goal is to keep label and labels in sync and update both at the same time for any changes. Where this is possible. A single name format will not solve every use case, so multiple variants are returned and there is a few options to affect how they get build. The general name convention is {organization}-{environment}-{name}-{attributes}. Name is required, the other 3 can be turned on/off ind
| Name | Type | Description | Default |
|---|---|---|---|
| environment | any | Environment (ex: `dev`, `qa`, `stage`, `prod`). (Second or top level namespace. | required |
| names | any | Base names for resources | required |
| namespace-env | any | Prefix name with the environment. If true, format is: <env>-<name> | true |
| tags | any | A map of additional tags | {} |
| team | any | TAG: Department/team of people responsible for service | "UNDEF" |
| attributes | any | Suffix name with additional attributes (policy, role, etc.) | [] |
| component | any | TAG: Underlying, dedicated piece of service (Cache, DB, ...) | "UNDEF" |
| delimiter | any | Delimiter to be used between `name`, `namespaces`, `attributes`, etc. | "-" |
| monitor | any | TAG: Should resource be monitored | "UNDEF" |
| namespace-org | any | Prefix name with the organization. If true, format is: <org>-<env namespaced nam | false |
| organization | any | Organization name (Top level namespace) | "" |
| owner | any | TAG: Owner of the service | "UNDEF" |
| product | any | TAG: Company/business product | "UNDEF" |
| service | any | TAG: Application (microservice) name | "UNDEF" |
| enabled | any | Set to false to prevent the module from creating anything | true |
attributes — Attribute string lowercaseenvironment — Environment name lowercaseid — Fully formatted name IDid_20 — ID truncated to 20 charactersid_32 — ID truncated to 32 charactersid_attr_20 — ID max size 20 characters by truncating `id_org` then appending `attributes`id_attr_32 — ID max size 32 characters by truncating `id_org` then appending `attributes`id_env — If env namespace enabled <env>-<name> else <name>id_org — If org namespace enabled <org>-<id_env> else <id_env>name — Name lowercaseorganization — Organization name lowercasetagsorg_attr_20 — Internal debugging. DO NOT USEorg_attr_32 — Internal debugging. DO NOT USEAzure landing zones Terraform module
Terraform supermodule for the Terraform platform engineering for Azure
Terraform module to deploy landing zone subscriptions (and much more) in Azure
Terraform Module to define a consistent naming convention by (namespace, stage,