![]() ![]() The minimum supported Terraform version is 0.12.0. ![]() The Terraform stage must use the same Terraform version that your Terraform Cloud/Enterprise workspace is configured to run.When using remote backends, keep the following in mind: The Terraform Integration feature supports using remote backends provided by Terraform Cloud and Terraform Enterprise. This example manifest also enables the Terraform Integration UI. If you already have a Git Repo artifact account configured in Spinnaker,Įdit the SpinnakerService manifest to add the following:ĪpiVersion : /v1alpha2 kind : SpinnakerService metadata : name : spinnaker spec : spinnakerConfig : config : armory : terraform : enabled : true profiles : deck : # Enables the UI for the Terraform Integration stage settings-local.js : | = true Spinnaker uses the Git Repo Artifact Provider to download the repo containing your main Terraform templates To fetch single files such as var-files or backend config files. Git Repo - To fetch the repo housing your main Terraform files.The Terraform Integration uses the following artifact accounts: The SSO option for the organizations that host the Terraform template(s) and Terraform tfvar files.įor more information about how to generate a GitHub PAT, see Creating a Personal Access Token for the Command Line. If your GitHub organization uses Single Sign-On (SSO), enable.The token uses a distinct name and has the repo scope.Make sure the PAT you create meets the following requirements: Additionally, the Spinnaker GitHub artifact provider require a PAT for tfvar files. You must create and configure a PAT so that the Terraform Integration can pull a directory of Terraform Templates from GitHub. The Terraform Integration authenticates itself using the PAT to interact with your GitHub repositories. Skip this section if you are using BitBucket, which requires your username and password.īefore you start, you need a GitHub Personal Access Token (PAT). Generate a GitHub Personal Access Token (PAT) Kubectl -n spinnaker apply -f spinnakerservice.yml To set/override the Armory Continuous Deployment Redis settings do the following: Note: The Terraform Integration feature can only be configured to use a password with the default Redis user. The Terraform Integration uses Redis to store Terraform logs and plans. This is to ensure that you do not encounter scaling or stability issues in production. Armory requires configuring a dedicated external Redis instance for production usage of the Terraform Integration.The Terraform Integration supports the following artifact providers for tfvar files and backend configs: You must have a separate artifact provider that can pull your tfvar file(s). A source for Terraform Input Variable Files ( tfvar) or a backend config.basic auth in the form of a user and password, or a user-password file.SSH protocol in the form of an SSH key or an SSH key file.For more information, see Generating a Github Personal Access Token (PAT). a Personal Access Token (potentially associated with a service account).Git Repo can be configured with any of the following:.The Terraform Integration needs access to credentials to download directories that house your Terraform templates. Credentials (in the form of basic auth) for the Git repository where your Terraform scripts are stored.Note that all Terraform stages within a pipeline that affects state must use the same Terraform version. When creating a Terraform Integration stage, pipeline creators select a specific available version from a list of available versions: The Terraform binaries are verified by checksum and with Hashicorp’s GPG key before being installed into an Armory release. Supported Terraform versionsĪrmory ships several versions of Terraform as part of the Terraform Integration feature. The integration interacts with a source repository you specify to deploy your infrastructure as part of a Spinnaker pipeline. ![]() For information about how to use the stage, see Use the Terraform Integration Stage in Armory Continuous Deployment.Īrmory’s Terraform Integration feature integrates your infrastructure-as-code Terraform workflow into your SDLC. Note that the Terraform Integration stage also requires a git/repo artifact account. The examples on this page describe how to configure the Terraform Integration stage and an artifact provider to support either GitHub or BitBucket. Overview of Terraform Integration in Spinnaker Learn how to configure the Terraform Integration stage so that app developers can provision infrastructure using Terraform as part of their delivery pipelines. Use Canary Analysis with AWS CloudWatch. ![]()
0 Comments
Leave a Reply. |