Connect Any Git or Mercurial Repo to Pulumi with Custom VCS

Why It Matters

Enterprises using self‑hosted or non‑standard VCS can now automate infrastructure deployments without scattering credentials, improving security and operational efficiency.

Key Takeaways

• Supports any Git or Mercurial server via org-level integration
• Centralizes credentials using Pulumi ESC, eliminating per‑stack secrets
• Enables webhook‑driven push‑to‑deploy automation for self‑hosted repos
• Lacks PR comments and status checks compared to native integrations
• Neo AI can clone and push but cannot create pull requests

Pulse Analysis

The rise of self‑hosted version‑control platforms has left many DevOps teams unable to fully automate infrastructure as code workflows. Pulumi’s existing native integrations cover the major cloud‑based services, but teams running private GitLab instances, Bitbucket Server, or legacy Mercurial repositories faced manual credential management and the loss of push‑to‑deploy triggers. By introducing Custom VCS, Pulumi bridges that gap, allowing organizations to register any repository at the organization level and store access tokens, SSH keys, or passwords securely in Pulumi ESC. This centralization reduces secret sprawl and aligns with best‑practice secret‑management policies.

Custom VCS leverages webhook callbacks to fire deployments automatically when code is pushed, mirroring the experience of native GitHub, GitLab, and Azure DevOps integrations. Users can filter by branch or path, ensuring only relevant changes trigger updates. However, the solution deliberately omits deeper platform‑specific features such as pull‑request comments, commit status checks, and review stack creation, which remain exclusive to native integrations. For teams that need those collaborative capabilities, the recommendation is to stick with the built‑in connectors; for pure deployment automation, Custom VCS offers a lightweight, vendor‑agnostic alternative.

From an industry perspective, the move signals a broader trend toward flexible, API‑driven IaC pipelines that accommodate heterogeneous toolchains. Companies adopting hybrid cloud strategies often maintain on‑premises code repositories for compliance reasons; Custom VCS enables them to extend Pulumi’s declarative infrastructure model without compromising security or requiring duplicate CI pipelines. As more organizations prioritize unified secret management and automated delivery, Pulumi’s Custom VCS is likely to become a standard component in multi‑cloud DevOps toolsets, especially when paired with Neo’s AI‑assisted repository actions.