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. 13 Feb, 2020 1 commit
  2. 11 Oct, 2019 1 commit
  3. 10 Apr, 2019 1 commit
  4. 25 Feb, 2019 1 commit
    • James Bardin's avatar
      Change backend.ValidateConfig to PrepareConfig · c814f2da
      James Bardin authored
      This mirrors the change made for providers, so that default values can
      be inserted into the config by the backend implementation. This is only
      the interface and method name changes, it does not yet add any default
      values.
      c814f2da
  5. 22 Feb, 2019 1 commit
  6. 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
  7. 06 Nov, 2018 1 commit
  8. 17 Oct, 2018 4 commits
  9. 03 Aug, 2018 3 commits
  10. 30 Oct, 2017 1 commit
    • stack72's avatar
      Migrate Manta Remote state to be a backend · 1fd0f803
      stack72 authored
      This PR changes manta from being a legacy remote state client to a new backend type. This also includes creating a simple lock within manta
      
      This PR also unifies the way the triton client is configured (the schema) and also uses the same env vars to set the backend up
      
      It is important to note that if the remote state path does not exist, then the backend will create that path. This means the user doesn't need to fall into a chicken and egg situation of creating the directory in advance before interacting with it
      1fd0f803
  11. 27 Oct, 2017 2 commits
  12. 08 Sep, 2017 2 commits
  13. 17 Aug, 2017 4 commits
  14. 13 Jun, 2017 1 commit
    • Gavin Williams's avatar
      remote/swift: Migrate Swift remote state to a backend · ee2e390f
      Gavin Williams authored
      Move the Swift State from a legacy remote state to an official backend.
      Add `container` and `archive_container` configuration variables, and deprecate `path` and `archive_path` variables.
      
      Future improvements: Add support for locking and environments.
      ee2e390f
  15. 22 Mar, 2017 1 commit
    • James Bardin's avatar
      convert S3 remote state to a backend · 9f5cf2b1
      James Bardin authored
      Move the S3 State from a legacy remote state to an official backend.
      
      This increases test coverage, uses a set schema for configuration, and
      will allow new backend features to be implemented for the S3 state, e.g.
      "environments".
      9f5cf2b1
  16. 01 Mar, 2017 1 commit
  17. 22 Feb, 2017 2 commits