env zero connects directly to your Git repository to trigger infrastructure deployments. env zero enables teams to connect their code repositories. This connection keeps your infrastructure code in sync by automatically updating env zero whenever your repository changes. This means less manual work, consistent environments, better tracking of changes, and improved teamwork between developers and operations. Integrating your VCS is a key enabler of a GitOps workflow. For example, env zero’s Pull Request (PR) plans automatically trigger a plan for your infrastructure code whenever changes are committed. This allows teams to continue using their familiar tools while env zero enhances their Infrastructure as Code (IaC) processes with features like PR plan/apply via comments and Continuous Deployment. These capabilities automate PR plan triggers, generate pull requests for review, and apply updates to your infrastructure. Continuous Deployment further simplifies workflows by automatically redeploying and executing the complete IaC lifecycle - initializing, planning, and applying - with each code commit. This results in faster iteration within testing environments and reduces the need for manual reviews. With VCS integration, you gain access to all these capabilities:Documentation Index
Fetch the complete documentation index at: https://docs.envzero.com/llms.txt
Use this file to discover all available pages before exploring further.
- Plan on Pull Request
- Continuous Deployment
- PR Comments Commands
- Module Registry
- Project-level Custom Flow
- Approval Policies
- Create a pull request (Code Generation)
- GitHub
- GitLab
- Bitbucket
- Azure DevOps
- GitHub Enterprise Server (Self-Hosted)
- Bitbucket Data Center (Server) (Self-Hosted)
- Offline GitLab (Self-Hosted)
- Git Server (Self-Hosted) - This basic integration allows actions like git clone, but does not support advanced features such as automated PR plans or Continuous Deployment.
Centralized Management
All your VCS integrations can be managed and configured under the Organization settings. Go to your Organization Settings and select the VCS tab. From there, you can edit existing connections or create new ones.
- In this modal, select the relevant VCS provider. Options are separated into Cloud and Self-Hosted categories.
- Choose env zero Access
- If you see the label ‘Not Configured,’ it indicates that this connection has not yet been saved in env zero.
- Choose Authentication Type
- Each VCS supports different Authentication Types. If only one option is available, it will be selected by default.
- Provide the necessary authentication information.
- Click ‘Save Connection’ to save these details to env zero.
- Remember to click ‘Save’ to apply any changes you make to the VCS connection.
VCS Actions
Within this modal, please confirm that the appropriate connection type is chosen. Additionally, you can perform the following actions:- Delete Connection
- Deleting the connection here will remove all related details from env zero. To revoke access from the VCS itself, you’ll need to do so within your VCS provider’s settings.
- Display connection health
- Display Available Repositories
- Display Webhook Settings - These are the settings you need to configure within your self-hosted VCS to enable automatic triggering of features.
Connection Types
Repositories AccessFor any connection type, you can specify which repositories env zero can access. For example, you might grant env zero access to both
repoX and repoY for deployments, but limit code writing access to only repoX.- Deployment
- Using this connection, env zero can deploy resources for your organization and enable all the features offered by CI/CD and governance. Available for all supported VCS providers.
- Code Write
- This connection allows env zero to commit code changes and generate AI-driven pull requests on your behalf. This capability powers features such as automatically creating pull requests to synchronize cloud environment changes with your code repository. Available for GitHub and Self-Hosted VCS providers.
Authentication Types
- OAuth
- When you click the ‘Grant Access’ button, a pop-up window will appear. You’ll need to authorize env zero to access your resources. After the pop-up closes (if successful), click ‘Save Connection’.
- By VCS Agent
- You need to have an active VCS Agent running. Then, provide the VCS URL and select the specific VCS Agent that env zero should connect to.
Next steps
- Standard GitHub Integration - Connect GitHub repositories to env zero.
- Standard Gitlab Integration - Connect GitLab repositories to env zero.
- Standard Bitbucket Integration - Connect Bitbucket repositories to env zero.
- Template Overview - Learn how templates use VCS connections for deployments.