A Terraform provider for managing Spinnaker applications, pipelines, and templates as infrastructure-as-code.
terraform-provider-spinnaker is a Terraform provider that allows users to manage Spinnaker applications, pipelines, and templates as infrastructure-as-code. It solves the problem of manual and inconsistent Spinnaker configuration by enabling declarative management through Terraform, facilitating automation and version control in continuous delivery pipelines.
DevOps engineers, platform engineers, and SREs who use Spinnaker for continuous delivery and want to automate and version-control their deployment configurations.
Developers choose this provider to bring Terraform's infrastructure-as-code benefits to Spinnaker, ensuring reproducible, auditable, and automated management of applications and pipelines, reducing manual overhead and configuration drift.
A Spinnaker provider for Terraform
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enables pipelines to be defined as code using JSON or YAML files, facilitating version control and automation, as demonstrated in the example with file('pipelines/example.json').
Supports DCD Spec pipeline templates for reusable and parameterized definitions, promoting consistency across deployments via resources like spinnaker_pipeline_template.
Offers configurable options such as custom headers and certificate error handling, allowing adaptation to various Spinnaker gate setups, as detailed in the provider arguments.
Integrates directly into existing Terraform workflows, enabling Spinnaker management alongside other infrastructure resources with declarative syntax.
The README explicitly states it is 'experimental and not supported by Armory for production use,' making it unreliable for critical deployments.
Only covers basic resources (applications, pipelines, templates), potentially missing advanced Spinnaker features like triggers, canary configs, or integrations.
Requires building from source with Go or manual plugin installation, which is more involved compared to official, maintained Terraform providers.