Right now an environment defines two different levels:
Application configuration, such as database type, logging and test runner (eg, django settings)
Instance configuration such as database instance, passwords, ips (eg, pillar context)
Let's review a few examples: dev is an environment of the first case without instance configuration (everything is local), but desicon and shared are a specific instances of the application environment production.
Splitting it makes sense because deployment depends on the higher-level env only, so using a targeting like G@env:production would be a lot easier than G@shared or G@env:desicon or.... Need to decice on a name for that entity..
Right now an environment defines two different levels:
Let's review a few examples: dev is an environment of the first case without instance configuration (everything is local), but desicon and shared are a specific instances of the application environment production.
Splitting it makes sense because deployment depends on the higher-level env only, so using a targeting like
G@env:productionwould be a lot easier thanG@shared or G@env:desicon or.... Need to decice on a name for that entity..