133 Commits (76eb65c911fcf1fcff030bef4e19807cab227aae)

Author	SHA1	Message	Date
Martin Atkins	2e0c1d07ae	Merge #15793: Locking support in HTTP remote backend	9 years ago
Ross McFarland	d889ac38b0	Change remote/http store to update, more consistent with doc	9 years ago
Ross McFarland	510563b67f	Fully test conf handling in httpFactory	9 years ago
Ross McFarland	69546c4b33	Pass at much more flexible remote/http backend ... - Configurable Put (store) method, default POST to preserve behavior - Configurable Lock method & address - Configurable Unlock method & address More thorough testing still needed, but this if functional	9 years ago
James Bardin	68da0390b7	remove legacy azure remote state code ... The implementation has been moved to a backend.	9 years ago
Peter McAtominey	f9e8e54835	backend: convert Azure remote state to a backend ... Added locking support via blob leasing (requires that an empty state is created before any lock can be acquired. Added support for "environments" in much the same way as the S3 backend.	9 years ago
Ross McFarland	6cdea5af5d	Clean up code and make the state/http behavior more consistent	9 years ago
Ross McFarland	ce4d9fb3c2	Add tests for state/http with locking	9 years ago
Ross McFarland	1d38569c91	Add Lock/Unlock support to remote/http	9 years ago
James Bardin	32ae05c342	fix strict remote.State lineage check ... We can't check lineage in the remote state instance, because we may need to overwrite a state with a new lineage. Whil it's tempting to add an optional interface for this, like OverwriteState(), optional interfaces are never _really_ optional, and will have to be implemented by any wrapper types as well. Another solution may be to add a State.Supersedes field to indicate that we intend to replace an existing state, but that may not be worth the extra check either.	9 years ago
Martin Atkins	4d53eaa6df	state: more robust handling of state Serial ... Previously we relied on a constellation of coincidences for everything to work out correctly with state serials. In particular, callers needed to be very careful about mutating states (or not) because many different bits of code shared pointers to the same objects. Here we move to a model where all of the state managers always use distinct instances of state, copied when WriteState is called. This means that they are truly a snapshot of the state as it was at that call, even if the caller goes on mutating the state that was passed. We also adjust the handling of serials so that the state managers ignore any serials in incoming states and instead just treat each Persist as the next version after what was most recently Refreshed. (An exception exists for when nothing has been refreshed, e.g. because we are writing a state to a location for the first time. In that case we _do_ trust the caller, since the given state is either a new state or it's a copy of something we're migrating from elsewhere with its state and lineage intact.) The intent here is to allow the rest of Terraform to not worry about serials and state identity, and instead just treat the state as a mutable structure. We'll just snapshot it occasionally, when WriteState is called, and deal with serials _only_ at persist time. This is intended as a more robust version of #15423, which was a quick hotfix to an issue that resulted from our previous slopping handling of state serials but arguably makes the problem worse by depending on an additional coincidental behavior of the local backend's apply implementation.	9 years ago
Gavin Williams	96e6bf89ec	remote/swift: Remove un-used code	9 years ago
Gavin Williams	ee2e390f85	remote/swift: Migrate Swift remote state to a backend ... 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.	9 years ago
James Bardin	808b504bcf	rename openstack provider for swift remote state	9 years ago
Tom Harvey	13583b4b8b	provider/azurerm: Upgrading to AutoRest v8 (#15006) ... * Upgrading to AutoRest 8 * Upgrading to AutoRest v8 * Updating the Remote State to v8	9 years ago
Tom Harvey	df2875045d	provider/azurerm: Upgrading to v10 of the Azure SDK (#14004) ... provider/azurerm: Upgrading to v10.0.2 of the Azure SDK	9 years ago
James Bardin	f0f2220abb	add mutexes to remote.State	9 years ago
Gavin Williams	c63ad9c0f8	state/remote/swift: Support Openstack request logging (#13583) ... * provider/openstack: Expose LogRoundTripper fields externally * state/remote/swift: Add support for debugging Openstack calls using OS_DEBUG env variable. * provider/openstack: Update LogRoundTripper to log headers aswell as body. * Add `RedactHeaders` function in order to redact sensitive http Headers. Refactor `logRequest` and `logResponse` to use `RedactHeaders` func.	9 years ago
James Bardin	9f5cf2b105	convert S3 remote state to a backend ... 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".	9 years ago
Ash Berlin	70de22253a	Fix error message in Azure state backend (#12424) ... The error led me to try adding `resource_group` but the code wanted `resource_group_name`. This fixes the error message to match the code.	9 years ago
Peter McAtominey	cbed463b44	state/azure: add environment option for non-public cloud usage (#12364)	9 years ago
Mitchell Hashimoto	942572b574	backend/init: add atlas, remove legacy atlas remote state	9 years ago
James Bardin	7f40f90c4c	remove the legacy Inmem remote state ... moved to a new backend	9 years ago
Mitchell Hashimoto	03f6c650ca	state/remote: ClientLocker is just a Client that is a state.Locker	9 years ago
Mitchell Hashimoto	9451acc5da	state/remote: add unit test to verify s3 is a ClientLocker as well	9 years ago
Mitchell Hashimoto	efe754183b	state/remote: export ClientLocker, test for implementation ... This adds unit tests (that will fail at compile time) if various structs don't implement the right interfaces for locking	9 years ago
James Bardin	ec00564be6	Clean up LockInfo and LockError and use them ... Gove LockInfo a Marshal method for easy serialization, and a String method for more readable output. Have the state.Locker implementations use LockError when possible to return LockInfo and an error.	9 years ago
James Bardin	888af93356	Have S3 check the lockID on Unlock ... This needs to be improved to happen in a transaction, but it gets the implementation passing the new tests.	9 years ago
James Bardin	67bbebce08	Have consul state reutrn the lock ID ... The lock ID isn't used because the lock is tied to the client, but return the lock ID to match the behavior of other locks.	9 years ago
James Bardin	6aa1066f7c	Store and use the correct IDs in TestRemoteLocks	9 years ago
James Bardin	f5ed8cd288	Use NewLockInfo to get a pre-populated value ... Using NewLockInfo ensure we start with all required fields filled.	9 years ago
James Bardin	6d32b70637	Make S3 remote state pass tests ... TODO: update S3Client to make full use of the state.Locker interface	9 years ago
James Bardin	0ad6f08204	Make remote state test run ... Make them compile against the new interface. The tests will be updated later to check new behavior.	9 years ago
James Bardin	4d00c29706	Merge pull request #11836 from hashicorp/jbardin/state-locking ... Add locking during backend configuration	9 years ago
Daren Desjardins	5718294386	state/remote/s3: Fix Bug with Assume Role for Federated IAM Account (#10067) ... * Enable remote s3 state support for assume role - provide role_arn in backend config to enable assume role Fixes #8739 * Check for errors after obtaining credentials	9 years ago
James Bardin	5c2e945b3c	Fix format string and typos	9 years ago
James Bardin	14d965722e	Use single state.LockInfo struct ... Remove redundant structures	9 years ago
James Bardin	9b76f6e138	Move TestRemoteLocks to state/remote ... This was legacy remote state client and backends can use this test function without an import cycle.	9 years ago
James Bardin	a2b5811f50	Remove "expires" from lock info. ... We are not going to handle lock expiration, at least at this time, so remove the Expires fields to avoid any confusion.	9 years ago
James Bardin	10f6d7f30f	Add locking for s3 state ... Use a DynamoDB table to coodinate state locking in S3. We use a simple strategy here, defining a key containing the value of the bucket/key of the state file as the lock. If the keys exists, the locks fails. TODO: decide if locks should automatically be expired, or require manual intervention.	9 years ago
James Bardin	35307d5a60	Add remote state locking ... In order to provide lockign for remote states, the Cache state, remote.State need to expose Lock and Unlock methods. The actual locking will be done by the remote.Client, which can implement the same state.Locker methods.	9 years ago
Mitchell Hashimoto	d3633ab368	state/remote: remove consul since we converted that	9 years ago
Ben Slusky	e3b20c3508	Basic authentication for HTTP remote state backend	9 years ago
Aleksander Modzelewski	2627e4bd8d	Add token authentication to Swift remote	9 years ago
Joe Topjian	8ecc6fda0a	Merge pull request #10055 from fatmcgav/swift_add_version_expire ... state/remote/swift: Add support for versioning state file in swift, and expiring objects	10 years ago
Gavin Williams	c77ed69a4e	state/remote/swift: Add support for versioning state file in swift, and expiring object after period of time. ... Update website docs with changes	10 years ago
Peter McAtominey	507efcb180	state/azure: support passing of lease ID when writing storage blob (#10115) ... Also fixed tests failing auth caused by getStorageAccountAccessKey returning the key name rather than the value TF_ACC= go test ./state/remote -v -run=TestAz -timeout=10m -parallel=4 === RUN TestAzureClient_impl --- PASS: TestAzureClient_impl (0.00s) === RUN TestAzureClient 2016/11/18 13:57:34 [DEBUG] New state was assigned lineage "96037426-f95e-45c3-9183-6c39b49f590b" 2016/11/18 13:57:34 [TRACE] Preserving existing state lineage "96037426-f95e-45c3-9183-6c39b49f590b" --- PASS: TestAzureClient (130.60s) === RUN TestAzureClientEmptyLease 2016/11/18 13:59:44 [DEBUG] New state was assigned lineage "d9997445-1ebf-4b2c-b4df-15ae152f6417" 2016/11/18 13:59:44 [TRACE] Preserving existing state lineage "d9997445-1ebf-4b2c-b4df-15ae152f6417" --- PASS: TestAzureClientEmptyLease (128.15s) === RUN TestAzureClientLease 2016/11/18 14:01:55 [DEBUG] New state was assigned lineage "85912a12-2e0e-464c-9886-8add39ea3a87" 2016/11/18 14:01:55 [TRACE] Preserving existing state lineage "85912a12-2e0e-464c-9886-8add39ea3a87" --- PASS: TestAzureClientLease (138.09s) PASS ok github.com/hashicorp/terraform/state/remote 397.111s	10 years ago
Gavin Williams	bf8612b9b7	state/remote/swift: Enhancements to support full set of Openstack configuration options, plus SSL certs. Documentation updated to support	10 years ago
Gavin Williams	ac07430124	state/remote/swift: Update to use Gophercloud/gophercloud, restructure to support insecure TLS, added Keystone v3 auth params ... Update swift remote documentation	10 years ago
Cameron Watters	b4eb63d710	state/remote: New provider - manta ... - add remote state provider backed by Joyent's Manta - add documentation of Manta remote state provider - explicitly check for passphrase-protected SSH keys, which are currently unsupported, and generate a more helpful error (borrowed from Packer's solution to the same problem): https://github.com/mitchellh/packer/blob/master/common/ssh/key.go#L27	10 years ago