A Terraform provider for managing Azure DevOps resources like projects, repositories, and pipelines as code.
Terraform Provider for Azure DevOps is an open-source plugin that enables managing Azure DevOps resources through Terraform. It solves the problem of manual, inconsistent configuration of DevOps projects, repositories, and pipelines by allowing teams to define everything as code. This ensures that DevOps environments are reproducible, version-controlled, and automated.
DevOps engineers, platform teams, and infrastructure developers who use Azure DevOps and want to adopt infrastructure as code practices for their CI/CD and project management tooling.
Developers choose this provider to bring Terraform's declarative, stateful management to Azure DevOps, eliminating configuration drift and enabling automated provisioning. Its tight integration with Terraform's ecosystem allows for unified infrastructure and DevOps management within a single workflow.
Terraform Azure DevOps provider
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Allows defining Azure DevOps resources like projects and pipelines in Terraform files, enabling version control and consistent deployments, as demonstrated in the usage example for projects, repositories, and build definitions.
Supports a wide array of resources including Git repositories, build definitions, and service connections, providing end-to-end automation capabilities as listed in the key features.
Maintained by Microsoft with active community support on Gitter and extensive documentation, ensuring reliability and up-to-date integrations with Azure DevOps features.
Integrates with the broader Terraform ecosystem, allowing combined management of cloud infrastructure and DevOps tooling in a single configuration, as highlighted in the value proposition.
Requires setting up multiple environment variables, installing Go and Terraform, and using Make or PowerShell scripts for development, which can be cumbersome and error-prone, as detailed in the developer requirements.
Acceptance tests provision actual Azure DevOps resources, incurring costs and requiring careful management of environment variables, as warned in the README section on environment variables for acceptance tests.
Tied specifically to Azure DevOps, so it cannot be used for managing resources in other DevOps platforms, limiting its versatility for multi-cloud or hybrid environments.