While our platform comes with a ever increasing portfolio of ready-to-use subsystems. Nothing beats having total control (as in Turing complete) of how your software is package and deployed.
For this cases, we have an special Shell subsystem featuring the ability to control three phases within the distribution pipeline:
Provision
Deployment
Clean up
Deployment Scripts
Under the familiar Deployment Agent Settings section you get access to manage the scripts that will execute on each phase. The following picture shows two (2) scripts set to run during the deployment phase:
Is very normal to reserve the first script to setup the dependencies of your deployment strategy. In this capture you can see how both bash and python are supported natively.
Environment Variables — CED symbols
Name | Value |
| Current organization |
| Current environment |
| Current project id |
| Current subsystem id |
| Current subsystem name |
| Current version id |
| Current version name |
| Absolute path to the artifact folder |
Environment Variables — CED Connections
CED_CONNECTION_<parameter-name>
Connection parameters are exposed in upper-snake-case. For instance, a connection parameter named adminApiKey will be exposed as:
CED_CONNECTION_ADMIN_API_KEY
Environment Variables — Self Configuration
CED_SUBSYSTEM_CONFIG_<parameter-name>
Subsystem configurations are exposed in upper-snake-case. For instance, a subsystem configuration named deploymentFolder will be exposed as:
CED_SUBSYSTEM_CONFIG_DEPLOYMENT_FOLDER.