Environment Configuration

Environment Configuration

Each environment has its own specific configuration that is the synthesis of the defaults from your Application Template and any overrides from the template your specific environment is based on.
Click 'VIEW' to view/edit the environment specific configuration
Click 'Edit' to view/edit the environment specific configuration
There are only a few structural differences between the default Application Template the Environment Specific Configuration found on the Environment Details page.
  • environment_templates The default configuration has this stanza to highlight differences between your ephemeral and permanent environments. A specific environment when created uses the correct template + defaults to generate the environment specific configuration.
  • datasets The datasets keyword can be included at the root of your environment specific configuration unlike in the Application Template. You can add and remove datasets for this particular environment.
Once you have created an environment it has an environment specific configuration file that all deployments will be based on. Changes in the default configuration (Application Template) will NOT change the file going forward. If you would like an environment to pick up changes in the default configuration you will need to delete the current one and make a new one, or just make a new one. This makes it very obvious and explicit where changes to the current environment are coming from.
Copy link