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. 26 Apr, 2022 1 commit
    • Sebastian Rivera's avatar
      Handle -input=false in cloud integration · 9d7fdbea
      Sebastian Rivera authored
      For non-interactive contexts, Terraform is typically executed with the flag -input=false.
      However for runs that are not set to auto approve, the cloud integration will prompt a user for
      approval input even with input being set to false. This commit enables the cloud integration to know
      the value of the input flag and use it to determine whether or not to ask the user for input.
      
      If -input is set to false and the run cannot be auto approved, the cloud integration will throw an error
      stating run confirmation can no longer be handled in the CLI and that they must do so through the browser.
      9d7fdbea
  2. 29 Oct, 2021 6 commits
    • Omar Ismail's avatar
      Add run variables to cloud plan operations from non-file sources · dd856f8a
      Omar Ismail authored
      Run variables allow the run API to accept input variables not found
      in the configuration slug (the file-based ones plus workspace vars)
      dd856f8a
    • Chris Arcand's avatar
      cloud: Set minimum TFE version · 7cc53fe1
      Chris Arcand authored
      These changes remove all of the preexisting version checking for
      individual features, wiping the slate clean with an overall minimum
      requirement of a future TFP-API-Version 2.5, which at the time of this
      writing is expected to be TFE v202112-1.
      
      It also actually provides that expected TFE version as an actionable
      error message, rather than generically saying that it isn't supported or
      using the somewhat opaque API version header.
      7cc53fe1
    • Omar Ismail's avatar
      Add auto-approve logic, e2e tests · a387af6c
      Omar Ismail authored
      a387af6c
    • Omar Ismail's avatar
      Use context parallelism · 594a390f
      Omar Ismail authored
      594a390f
    • Chris Arcand's avatar
      a5f06362
    • Chris Arcand's avatar
      Initial commit of 'cloud' package · ea8ad0b1
      Chris Arcand authored
      The cloud package intends to implement a new integration for
      Terraform Cloud/Enterprise. The purpose of this integration is to better
      support TFC users; it will shed some overly generic UX and architecture,
      behavior changes that are otherwise backwards incompatible in the remote
      backend, and technical debt - all of which are vestiges from before
      Terraform Cloud existed.
      
      This initial commit is largely a porting of the existing 'remote'
      backend, which will serve as an underlying implementation detail and not
      be a typical user-level backend. This is because to re-implement the
      literal backend interface is orthogonal to the purpose of this
      integration, and can always be migrated away from later.
      
      As this backend is considered an implementation detail, it will not be
      registered as a declarable backend. Within these changes it is, for easy
      of initial development and a clean diff.
      ea8ad0b1
  3. 14 Sep, 2021 1 commit
    • Martin Atkins's avatar
      backend: Remove Operation.Parallelism field · 718fa389
      Martin Atkins authored
      The presence of this field was confusing because in practice the local
      backend doesn't use it for anything and the remote backend was using it
      only to return an error if it's set to anything other than the default,
      under the assumption that it would always match ContextOpts.Parallelism.
      
      The "command" package is the one actually responsible for handling this
      option, and it does so by placing it into the partial ContextOpts which it
      passes into the backend when preparing for a local operation. To make that
      clearer, here we remove Operation.Parallelism and change the few uses of
      it to refer to ContextOpts.Parallelism instead, so that everyone is
      reading and writing this value from the same place.
      718fa389
  4. 18 May, 2021 1 commit
  5. 17 May, 2021 5 commits
    • Chris Arcand's avatar
      cb49a4c8
    • Martin Atkins's avatar
      Move terraform/ to internal/terraform/ · 36d0a504
      Martin Atkins authored
      This is part of a general effort to move all of Terraform's non-library
      package surface under internal in order to reinforce that these are for
      internal use within Terraform only.
      
      If you were previously importing packages under this prefix into an
      external codebase, you could pin to an earlier release tag as an interim
      solution until you've make a plan to achieve the same functionality some
      other way.
      36d0a504
    • Martin Atkins's avatar
      Move plans/ to internal/plans/ · 034e9440
      Martin Atkins authored
      This is part of a general effort to move all of Terraform's non-library
      package surface under internal in order to reinforce that these are for
      internal use within Terraform only.
      
      If you were previously importing packages under this prefix into an
      external codebase, you could pin to an earlier release tag as an interim
      solution until you've make a plan to achieve the same functionality some
      other way.
      034e9440
    • Martin Atkins's avatar
      Move tfdiags/ to internal/tfdiags/ · 05caff2c
      Martin Atkins authored
      This is part of a general effort to move all of Terraform's non-library
      package surface under internal in order to reinforce that these are for
      internal use within Terraform only.
      
      If you were previously importing packages under this prefix into an
      external codebase, you could pin to an earlier release tag as an interim
      solution until you've make a plan to achieve the same functionality some
      other way.
      05caff2c
    • Martin Atkins's avatar
      Move backend/ to internal/backend/ · 73dda868
      Martin Atkins authored
      This is part of a general effort to move all of Terraform's non-library
      package surface under internal in order to reinforce that these are for
      internal use within Terraform only.
      
      If you were previously importing packages under this prefix into an
      external codebase, you could pin to an earlier release tag as an interim
      solution until you've make a plan to achieve the same functionality some
      other way.
      73dda868
  6. 27 Apr, 2021 1 commit
    • Martin Atkins's avatar
      command+backend: generalized "plan mode" · 89f986de
      Martin Atkins authored
      So far we've only had "normal mode" and "destroy mode", where the latter
      is activated either by "terraform plan -destroy" or "terraform destroy".
      
      In preparation for introducing a third mode "refresh only" this
      generalizes how we handle modes so we can potentially deal with an
      arbitrary number of modes, although for now we only intend to have three.
      
      Mostly this is just a different implementation of the same old behavior,
      but there is one small user-visible difference here: the "terraform apply"
      command now accepts a -destroy option, mirroring the option of the same
      name on "terraform plan", which in turn makes "terraform destroy"
      effectively a shorthand for "terraform apply -destroy".
      
      This is intended to make us consistent that "terraform apply" without a
      plan file argument accepts all of the same plan-customization options that
      "terraform plan" does, which will in turn avoid us having to add a new
      alias of "terraform plan" for each new plan mode we might add. The -help
      output is changed in that vein here, although we'll wait for subsequent
      commit to make a similar change to the website documentation just so we
      can deal with the "refresh only mode" docs at the same time.
      89f986de
  7. 03 Feb, 2021 1 commit
  8. 15 May, 2020 2 commits
  9. 18 Oct, 2019 1 commit
    • Martin Atkins's avatar
      backend/remote: Report invalid variables only remotely · a8d01e39
      Martin Atkins authored
      The remote backend uses backend.ParseVariableValues locally only to decide
      if the user seems to be trying to use -var or -var-file options locally,
      since those are not supported for the remote backend.
      
      Other than detecting those, we don't actually have any need to use the
      results of backend.ParseVariableValues, and so it's better for us to
      ignore any errors it produces itself and prefer to just send a
      potentially-invalid request to the remote system and let the remote system
      be responsible for validating it.
      
      This then avoids issues caused by the fact that when remote operations are
      in use the local system does not have all of the required context: it
      can't see which environment variables will be set in the remote execution
      context nor which variables the remote system will set using its own
      generated -var-file based on the workspace stored variables.
      a8d01e39
  10. 14 Jun, 2019 1 commit
  11. 08 Mar, 2019 1 commit
  12. 25 Feb, 2019 1 commit
  13. 07 Feb, 2019 1 commit
  14. 08 Jan, 2019 1 commit
  15. 20 Nov, 2018 1 commit
    • Sander van Harmelen's avatar
      Change how to fall back from remote to local backend · a17f3170
      Sander van Harmelen authored
      In order to support free organizations, we need a way to load the `remote` backend and then, depending on the used offering/plan, enable or disable remote operations.
      
      In other words, we should be able to dynamically fall back to the `local` backend if needed, after first configuring the `remote` backend.
      
      To make this works we need to change the way this was done previously when the env var `TF_FORCE_LOCAL_BACKEND` was set. The clear difference of course being that the env var would be available on startup, while the used offering/plan is only known after being able to connect to TFE.
      a17f3170
  16. 06 Nov, 2018 1 commit
  17. 17 Oct, 2018 1 commit
    • Martin Atkins's avatar
      Revert some work that happened since v0.12-dev branched · 541952bb
      Martin Atkins authored
      This work was done against APIs that were already changed in the branch
      before work began, and so it doesn't apply to the v0.12 development work.
      
      To allow v0.12 to merge down to master, we'll revert this work out for now
      and then re-introduce equivalent functionality in later commits that works
      against the new APIs.
      541952bb
  18. 16 Oct, 2018 1 commit
  19. 15 Oct, 2018 1 commit
  20. 11 Oct, 2018 2 commits
  21. 09 Oct, 2018 1 commit
  22. 08 Oct, 2018 1 commit
  23. 05 Oct, 2018 2 commits
  24. 04 Oct, 2018 1 commit
  25. 02 Oct, 2018 1 commit
    • Sander van Harmelen's avatar
      Only show the full policy output when it fails · 37f5ab35
      Sander van Harmelen authored
      If the policy passes, only show that instead of the full check output to prevent cluttering the output. So a passing policy will only show:
      
      -----------------------------------------------
      Organization policy check: passed
      -----------------------------------------------
      37f5ab35
  26. 26 Sep, 2018 1 commit
  27. 22 Sep, 2018 2 commits