Creating an Environment
Environments in sfops is tied to GitHub Environments (https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment) with additional metadata such as described below\
| Name | Type | Purpose |
|---|---|---|
| SBXNAME | variable : string | (Optional) Stores the name of the sandbox associated with the environment. If SB_SFDX_AUTH_URL is not provided use, the name to handle authentication. Read more here |
| TESTRUN | variable : boolean | Use this environment for daily full test tuns by a scheduled sfops workflow |
| TYPE | variable : string | Denotes the type of the environment, an environment could be one of 'development', 'test' or 'release' |
| SB_SFDX_AUTH_URL | secret : string | Auth URL to the environment, Read here on how to generate one |
| BRANCH | variable:string | Required for test and snapshot environments. This variable denote the branch which environment is associated with. |
Environments added to GitHub will be displayed in Environment Snapshot in sfops Dev Central as shown below
Environments can be created from dev central by using the add icon in each of the category. One could also use the 'Request a new environment', from the service catalogue directly, where you could fill in the details, and the environment gets created. Please note the sandbox has to be created previously before triggering the request.
