For our Microsoft Azure resources we have a naming convention as follows:
{productName}-{stage}-{azureRegion}-{type}-{resourceType}[-{NN}]
Where:
- stage indicates the 'enviroment' or 'stage' of the software running on the infra, "dev", "test" or "prod"
- type is used to group resources into, "data" (e.g. databases), "app" or "shared" (e.g. networking).
We want all stages of the software to run on production grade infra. But now, when experimenting with new infra, the naming convention leaves no room for these experiments. This is a problem because some resource names need to be globally unigue resulting in clashes.
Question
How do others distinguish between the stage of the software and the stage of the infra in the naming convention?