Using an environment file

Environment files must be loaded before the installation of the components it is overriding in order for it to provide the configuration override values. Any components being overridden in the environment file will be installed during the loading of the environment file, along with any of their component dependencies.

To load an environment file, use the command:

manage_components.py env load <environment filename>

Where environment filename corresponds to the name of the .json file in the <instance>\environments directory.

You can only load one environment file at any given time. If an environment file has already been loaded and you try to load it again or try to load a different environment file, you will be presented with an error message akin to, An environment (environment name) is already loaded , and the environment file will fail to load. The reason for this is environments are intended to be applied before configuration starts to enter the system. Changing an environment file and reloading it requires the load to be forced to signify pushing new information, rather than changing incoming data, which is the standard intention of an environment file. This error will also occur if you have mistakenly loaded the wrong environment file and attempt to load the correct one afterwards.

To force the system to load the new environment file add " --force " to your load command:

manage_components.py env load <environment filename> --force

This command will cause Bravura Security Fabric to attempt a reload of any configuration data attached to installed components and make the configuration substitutions your environment file defines.