sfops
sfpSlackGithub
  • Overview
  • Features
  • Environments
    • Creating an Environment
    • Authenticating to Environments
    • Review Environments
      • Configuring Review Sandboxes
      • Creation and Allocation of Review Sandboxes
  • Project Workflows
    • sfops - Execute Issue Ops
    • sfops - On Pull Request Comments
    • sfops - Close Issues
    • sfops - Execute Every 30 mins
    • sfops - Daily Job Executor
    • sfops - Review Sandbox - Creator
    • sfops - On Push to Branch
    • sfops - Execute Releases to any env
    • sfops - Execute Releases
  • IssueOps
    • Access
      • Request elevated previlege in production
    • Release
      • Release a Domain
      • Hotfix Workflow
  • Changelog
    • November24
    • January25
  • DevCentral
    • Customising Menu
    • Extending using Custom Forms and Issue Ops Actions
  • self managed instances
    • Setup for self managed instances
      • 1. Create repositories
      • 2. Create a GitHub App
      • 3. Setting up sfops repository
      • 4. Trigger the workflows
      • 5. Setting up project repository
      • 6. Fetching upstream changes
        • 6.1 Manual Process for Updating sfops from Upstream
    • Update Instructions
      • Updating to v29.0.0
      • Updating to v30.3.1 and above
    • Workflow details
      • Sync Upstream Repository and Create Pull Request
  • Legal
    • Terms of Service for sfops
Powered by GitBook
On this page
  1. Environments

Creating an Environment

PreviousEnvironmentsNextAuthenticating to Environments

Last updated 2 months ago

Environments in sfops is tied to GitHub Environments () with additional metadata such as described below

Name
Type
Purpose

SBXNAME

variable : string

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

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.

(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

Auth URL to the environment, Read on how to generate one

here
here
https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment