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. 12 Jan, 2021 5 commits
  2. 11 Jan, 2021 15 commits
  3. 09 Jan, 2021 1 commit
    • Cladius Fernando's avatar
      Corrected minor typo · 25003a0c
      Cladius Fernando authored
      On Windows, the file must be named named terraform.rc => On Windows, the file must be named terraform.rc
      25003a0c
  4. 08 Jan, 2021 7 commits
    • James Bardin's avatar
      refactor context plan · fb2208a6
      James Bardin authored
      get rid of the mutation of the plans.Plan and return values.
      fb2208a6
    • James Bardin's avatar
      refresh is expected for destroy · e614fb9a
      James Bardin authored
      These tests were not previously running a refresh, and hence did not
      expect the resources to be read.
      e614fb9a
    • James Bardin's avatar
      refresh state during a destroy plan · 0b3b84ac
      James Bardin authored
      Because the destroy plan only creates the necessary changes for apply to
      remove all the resources, it does no reading of resources or data
      sources, leading to stale data in the state. In most cases this is not a
      problem, but when a provider configuration is using resource values, the
      provider may not be able to run correctly during apply. In prior
      versions of terraform, the implicit refresh that happened during
      `terraform destroy` would update the data sources and remove missing
      resources from state as required.
      
      The destroy plan graph has a minimal amount of information, so it is not
      feasible to work the reading of resources into the operation without
      completely replicating the normal plan graph, and updating the plan
      graph and all destroy node implementation is also a considerable amount
      of refactoring. Instead, we can run a normal plan which is used to
      refresh the state before creating the destroy plan. This brings back
      similar behavior to core versions prior to 0.14, and the refresh can
      still be skipped using the `-refresh=false` cli flag.
      0b3b84ac
    • James Bardin's avatar
      3e224df3
    • James Bardin's avatar
      ensure context cancel is never nil · 026ba5b0
      James Bardin authored
      The context used for Stop is more appropriately tied to the lifetime of
      the provisioner rather than a call to the ProvisionResource method. In
      some cases Stop can be called before ProvisionResource, causing a panic
      the provisioner.  Rather than adding nil checks to the CancelFunc call
      for Stop, create a base context to use for cancellation with both Stop
      and Close methods.
      026ba5b0
    • Pam Selle's avatar
      Merge pull request #27429 from hashicorp/pselle/staticcheck · d175e67b
      Pam Selle authored
      Staticcheck fixes in terraform package
      d175e67b
    • Alisdair McDiarmid's avatar
      cli: Fix rendering of long integers · d763e4f7
      Alisdair McDiarmid authored
      Recent changes to the human-readable rendering of outputs and console
      values led to long integer values being presented in scientific
      notation (e.g. 1.2345678e+07). While technically correct, this is an
      unusual way to present integer values.
      
      This commit changes the formatting mode to 'f', which never uses
      scientific notation and displays integer values as a sequence of digits
      instead (e.g. 12345678).
      d763e4f7
  5. 07 Jan, 2021 8 commits
  6. 06 Jan, 2021 4 commits