vcs-workflow

Automate GitLab VCS integration and workspace bindings for Terraform Enterprise deployments.

29|8|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/hashimiche/hal --skill vcs-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vcs-workflow
Source: https://github.com/hashimiche/hal/tree/main/internal/skills/data/terraform/vcs-workflow
Command: npx skills add https://github.com/hashimiche/hal --skill vcs-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the setup and ongoing management of VCS-driven Terraform workspace bindings.

Core Features & Use Cases

  • Bootstraps GitLab-based VCS integration for Terraform Enterprise workspaces.
  • Wires TFE workspaces to corresponding GitLab repositories and configures VCS triggers.
  • Supports multiple targets (primary and twin) via the --target flag to manage parallel deployments.

Quick Start

Run hal terraform vcs-workflow enable to bootstrap GitLab integration and workspace wiring.

Frequently Asked Questions about vcs-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Terraform Enterprise workspace bindings to GitLab repositories?

To automate Terraform Enterprise workspace bindings, you can use a VCS workflow that registers a GitLab OAuth application, links workspaces to repositories, and configures VCS triggers across primary and twin deployments.

Can I manage VCS-driven Terraform workspaces across multiple TFE deployments simultaneously?

Yes, you can manage VCS-driven Terraform workspaces across multiple TFE deployments simultaneously by using a target flag to apply integration updates and verify configurations across parallel primary and twin environments.

What is the process to bootstrap GitLab VCS integration for Terraform workspaces?

Bootstrapping GitLab VCS integration involves implementing required prerequisites, registering a GitLab OAuth application in TFE, creating or linking workspaces to repos, and configuring VCS triggers per workspace.

How do I enable or disable VCS triggers for a specific Terraform workspace?

You can enable or disable VCS triggers for a specific Terraform workspace by using workflow commands that update the workspace-to-GitLab integration settings and verify the connection status across targeted deployments.

Does this VCS workflow require setting up a GitLab OAuth application in TFE first?

Yes, setting up VCS-driven Terraform workspace automation requires registering a GitLab OAuth application in TFE as part of the prerequisites before creating or linking workspaces to repositories.

What are the limitations of using VCS-driven workspace automation for parallel TFE targets?

The automation manages primary and twin TFE deployments via a target flag, but users must independently ensure prerequisites are met and verify that VCS triggers are correctly configured per workspace across all parallel targets.