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.
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
- 24 Jun, 2020 3 commits
-
-
hashicorp-ci authored
-
James Bardin authored
-
James Bardin authored
Ensure that the *http.Response is not nil before checking the status.
-
- 05 Jun, 2020 3 commits
-
-
Chris Griggs authored
[Website Cherrypick] provider links
-
Chris Griggs authored
-
Chris Griggs authored
[Website] Update provider links
-
- 28 May, 2020 1 commit
-
-
Chris Griggs authored
-
- 27 May, 2020 4 commits
-
-
tf-release-bot authored
-
tf-release-bot authored
-
Martin Atkins authored
-
Paddy authored
This adds supports for "unmanaged" providers, or providers with process lifecycles not controlled by Terraform. These providers are assumed to be started before Terraform is launched, and are assumed to shut themselves down after Terraform has finished running. To do this, we must update the go-plugin dependency to v1.3.0, which added support for the "test mode" plugin serving that powers all this. As a side-effect of not needing to manage the process lifecycle anymore, Terraform also no longer needs to worry about the provider's binary, as it won't be used for anything anymore. Because of this, we can disable the init behavior that concerns itself with downloading that provider's binary, checking its version, and otherwise managing the binary. This is all managed on a per-provider basis, so managed providers that Terraform downloads, starts, and stops can be used in the same commands as unmanaged providers. The TF_REATTACH_PROVIDERS environment variable is...
-
- 19 May, 2020 8 commits
-
-
Martin Atkins authored
-
CJ Horton authored
-
CJ Horton authored
-
CJ Horton authored
-
CJ Horton authored
-
Mike Nomitch authored
-
Martin Atkins authored
Previously we did not allow -target to be used with the remote backend because there was no way to send the targets to Terraform Cloud/Enterprise via the API. There is now an attribute in the request for creating a plan that allows us to send target addresses, so we'll remove that restriction and copy the given target addresses into the API request.
-
Martin Atkins authored
This includes a new TargetAddrs field on both Run and RunCreateOptions which we'll use to send resource addresses that were specified using -target on the CLI command line when using the remote backend. There were some unrelated upstream breaking changes compared to the last version we had vendored, so this commit also includes some changes to the backend/remote package to work with this new API, which now requires the remote backend to be aware of the remote system's opaque workspace id.
-
- 18 May, 2020 1 commit
-
-
Paul Tyng authored
These are present on master. Without this cherry-pick, they can get dropped from the site if we do another 0.12 release.
-
- 13 May, 2020 4 commits
-
-
Chris Griggs authored
-
charlotte.mach authored
-
tf-release-bot authored
-
tf-release-bot authored
-
- 12 May, 2020 3 commits
-
-
Alisdair McDiarmid authored
vendor: go get golang.org/x/crypto@latest
-
Alisdair McDiarmid authored
Upgrade to fix CVE-2020-9283, a denial of service bug affecting SSH servers & clients.
-
Kristin Laemmert authored
Up until now, terraform would silently ignore any "source" attributes found in a required_provider block. This adds a warning when "source" is found informing users that the attribute is ignored in terraform v0.12. We were previously throwing away any warnings from the config loader if there were no errors, so as a side effect any other warnings out of the config loader that had not been displayed previously are now shown.
-
- 07 May, 2020 4 commits
-
-
Robin Norwood authored
-
Robin Norwood authored
-
Pam Selle authored
-
Pam Selle authored
Backport remote backend force push to v0.12
-
- 06 May, 2020 2 commits
-
-
Lee Trout authored
Both differing serials and lineage protections should be bypassed with the -force flag (in addition to resources). Compared to other backends we aren’t just shipping over the state bytes in a simple payload during the persistence phase of the push command and the force flag added to the Go TFE client needs to be specified at that time. To prevent changing every method signature of PersistState of the remote client I added an optional interface that provides a hook to flag the Client as operating in a force push context. Changing the method signature would be more explicit at the cost of not being used anywhere else currently or the optional interface pattern could be applied to the state itself so it could be upgraded to support PersistState(force bool) only when needed. Prior to this only the resources of the state were checked for changes not the lineage or the serial. To bring this in line with documented behavior noted above those attributes also have a “read” counterpart just like state has. These are now checked along with state to determine if the state as a whole is unchanged. Tests were altered to table driven test format and testing was expanded to include WriteStateForMigration and its interaction with a ClientForcePusher type.
-
Lee Trout authored
We only persist a new state if the actual state contents have changed. This test demonstrates that behavior by calling write and persist methods when either the lineage or serial have changed.
-
- 05 May, 2020 7 commits
-
-
James Bardin authored
-
James Bardin authored
-
James Bardin authored
Have the InstanceKey implementations handle their own cty.Value conversions.
-
James Bardin authored
-
James Bardin authored
During destroy, the for expression may be unknown and evaluation will fail. Destroy provisioners however can only reference the key value, which is known in the address.
-
Pam Selle authored
[Cherry-pick] Fix races in GetVariableValue and login #24599
-
James Bardin authored
-