This project is mirrored from https://:*****@github.com/hashicorp/terraform.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
  1. 07 Dec, 2021 1 commit
  2. 06 Dec, 2021 2 commits
  3. 03 Dec, 2021 3 commits
  4. 01 Dec, 2021 9 commits
  5. 30 Nov, 2021 5 commits
  6. 29 Nov, 2021 2 commits
  7. 26 Nov, 2021 1 commit
  8. 25 Nov, 2021 2 commits
  9. 24 Nov, 2021 1 commit
    • Alisdair McDiarmid's avatar
      core: Fix schema loading for deleted resources · 5ddf5e1f
      Alisdair McDiarmid authored
      Resource instances removed from the configuration would previously use
      the implied provider address. This is correct for default providers, but
      incorrect for those from other namespaces or hosts. The fix here is to
      use the stored provider config if it is present.
      5ddf5e1f
  10. 23 Nov, 2021 3 commits
    • Barrett Clark's avatar
      Merge pull request #29997 from hashicorp/barrettclark/cloud-input-false · a6b56ad7
      Barrett Clark authored
      Cloud integration requires input for migrations
      a6b56ad7
    • Barrett Clark's avatar
      Cloud integration requires input for migrations · 419676cb
      Barrett Clark authored
      We cannot programmatically migrate workspaces to Terraform Cloud without
      prompts, so `-input=false` should not be allowed in those cases.
      
      There are 4 scenarios where we need input from a user to complete
      migrating workspaces to Terraform Cloud.
      
      1.) Migrate from a single local workspace to Terraform Cloud
      
      * Terraform config for a local backend. Implicit local (no backend
        specified) is fine.
      * `terraform init` and `terraform apply`
      * Change the Terraform config to use the cloud block
      * `terraform init -input=false`
      * You should now see an error message
      
      2.) Migrate from a remote backend with a prefix to Terraform Cloud with
        tags
      
      * Create a workspace in Terraform Cloud manually. The name should
        include a prefix, like "app-one"
      * Have the terraform config use `backend "remote"` with a prefix set to
        "app-"
      * `terraform init` and `terraform apply`
      * Update the Terraform config to use a cloud block with `tags
        = ["app"]`. There should not be a prefix defined in the config now.
      * `terraform init -input=false`
      * You should now see an error message
      
      3.) Migrate from multiple local workspaces to a single Terraform Cloud
        workspace
      * Create one or many local workspaces
      * `terraform init` and `terraform apply` in each
      * Change the Terraform config to use the cloud block
      * `terraform init -input=false`
      * You should now see an error message
      
      4.) Migrate to Terraform Cloud and ask for a workspace name
      * Create several local workspaces
      * `terraform init` and `terraform apply` in each
      * Change the Terraform config to use the cloud block with tags
      * `terraform init -input=false`
      * You should now see an error message
      419676cb
    • Brandon Romano's avatar
      Merge pull request #30001 from hashicorp/revert-commit · ce1dbd7d
      Brandon Romano authored
      Revert "migrate docs to mdx"
      ce1dbd7d
  11. 22 Nov, 2021 4 commits
  12. 19 Nov, 2021 6 commits
  13. 18 Nov, 2021 1 commit