Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://developer.hashicorp.com/terraform/migrate below:

Migrate to HCP Terraform | Terraform

The tf-migrate CLI automatically migrates your Terraform Community Edition state and variable values to HCP Terraform or Terraform Enterprise. It also updates your local configuration with the new state storage location and optionally creates a pull request to update your code repository.

Hands-on: Complete the Migrate to HCP Terraform in bulk tutorial to get started with tf-migrate.

Complete the following steps to install and configure tf-migrate:

1. Download and install tf-migrate.
2. Configure tf-migrate to authenticate to HCP Terraform or Terraform Enterprise.
3. Optionally authenticate your VCS provider with your version control provider API key to create a pull request with your configuration changes.
4. Optionally enable logging so that you can troubleshoot potential issues that may occur during the migration process.

The tf-migrate tool supports migrating state from the following backends to HCP Terraform or Terraform Enterprise:

• local
• azurerm
• consul
• cos
• gcs
• http
• Kubernetes
• oss
• pg
• s3

The tf-migrate CLI does not support migrating state from an existing cloud integration or remote backend.

The tf-migrate tool can create CLI- or VCS-driven HCP Terraform workspaces. It will only prompt you to create a VCS-driven workspace if you meet the following requirements:

• Your local configuration is a Git repository.
• Your local Git repository has either GitHub or GitLab configured as a remote.
• Your HCP Terraform organization has at least one VCS OAuth connection configured for GitHub or GitLab.

If your HCP Terraform organization has more than one VCS connection configured, tf-migrate will ask you to choose which VCS connection to use.

If your local configuration does not meet all of the above requirements, tf-migrate automatically creates a CLI-driven workspace instead.

You can enable detailed logging by setting the TF_MIGRATE_ENABLE_LOG environment variable to true. When you enable this setting, tf-migrate writes the logs to the following locations, depending on your operating system:

You can set the TF_MIGRATE_LOG_LEVEL environment variable to one of the following values to change the verbosity of the logs in order of decreasing verbosity:

• TRACE
• DEBUG
• INFO
• WARN
• ERROR

You can create an optional configuration file to modify the tf-migrate CLI behavior and specify the path to the configuration file when you run tf-migrate prepare. Any command-line flags you provide with these commands override the configuration file. Refer to the configuration reference for additional information.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4