Deployment environments

Quantic

There are two deployment environments for Quantic: Quantic Staging and Quantic Production.

Those environments have identical sets of variables and secrets (same names and same values in both environments), which are used to authorize an org using the JWT flow when deploying Quantic:

• SFDX_AUTH_JWT_KEY_FILE (variable): The name of the private key file to pipe the SFDX_AUTH_JWT_KEY secret value into.
• SFDX_AUTH_JWT_USERNAME (variable): The SFDX user name.
• SFDX_AUTH_CLIENT_ID (secret): The SFDX JWT consumer key.
• SFDX_AUTH_JWT_KEY (secret): The SFDX JWT private RSA key.

The only difference between the Quantic Staging and Production environments is that Staging only enforces branch protection whereas Production also leverages the DX bot to automate approval of the last steps of the deployment process.

Quantic end-to-end tests are run in the global environment with a different set of consumer and private keys. However, the key file and user name are the same in end-to-end tests as in the Staging and Production environments. This implies that SFDX_AUTH_CLIENT_ID and SFDX_AUTH_JWT_KEY are also defined as repository secrets whereas SFDX_AUTH_JWT_KEY_FILE and SFDX_AUTH_JWT_USERNAME are not (since they are not sensitive values).

Quantic Staging

The create-quantic-package workflow uses this environment. This workflow is dispatched every day at 23:00 UTC.

Quantic Production

The quantic-prod job in the release workflow uses this environment. This workflow is dispatched every Wednesday at 13:00 UTC.