338 Commits (eac87798708e714fd3a7e2ae496bddc021a32fa0)

Author	SHA1	Message	Date
James Bardin	fbc11c7961	fix incorrect current state in local backend ... Forgot to remove the currentState field, which was not always set. The current state should always just be read from the environment file. Always return the default state name when we can't determine the state.	9 years ago
James Bardin	e6eb71dde5	Add tests to check Backend delegation ... Ensure that when MultiState methods are properly delegated when there is a defined Local.Backend.	9 years ago
James Bardin	0933541a8c	Split out the backend environment interface ... Split the interface to change environments out from the minimal Backend interface, to make it optional for backend implementations. If backend.MultiState isn't implemented, return a "not implemented" from environment related methods. Have the Local backend delegate the MultiState methods to the proper backend.	9 years ago
James Bardin	dbc45b907c	Make the Local backend handle its own named states ... Add the functionality required for terraform environments	9 years ago
James Bardin	761c63d14a	Update Backend to incorporate environments ... Add the missing methods/arguments to handle Terraform environments in Backends. Extra functionality simply returns defaults for now.	9 years ago
Mitchell Hashimoto	3cedfa00f4	command: use backend.CLIIinit ... I made this interface way back with the original backend work and I guess I forgot to hook it up! This is becoming an issue as I'm working on our 2nd enhanced backend that requires this information and I realized it was hardcoded before. This propertly uses the CLIInit interface allowing any backend to gain access to this data.	9 years ago
Mitchell Hashimoto	8f11068ab2	Merge pull request #12173 from hashicorp/b-remote-state-ds ... providers/terraform: remote state data source supports backends	9 years ago
Mitchell Hashimoto	d2d87bccf0	Merge pull request #12155 from hashicorp/b-state-backend ... command: refresh state in old commands for backend	9 years ago
Mitchell Hashimoto	9574f16f92	backend/local: refresh with no config should not crash on input ... Fixes #12174 You're allowed to refresh with a nil module (no configs) as long as you have state. However, if `-input=true` (default) then this would crash since the input attempts to read the configs. The API contract with `terraform.Context` says that the module tree must be non-nil and loaded. To do this for other commands we create an empty module tree. We do that here now.	9 years ago
Mitchell Hashimoto	ebb22d3ecd	backend/local: don't RefreshState on State API	9 years ago
Mitchell Hashimoto	52720ce880	providers/terraform: data source uses backends for state loading	9 years ago
Mitchell Hashimoto	f79e04500f	backend/init: a package for storing the factories for backends	9 years ago
James Bardin	2392455a67	Add inmem remote backend ... Add an Inmem remote state backend. The only config option right now is a lock_id, which will instantiate the backend in a locked state for testing.	9 years ago
Mitchell Hashimoto	d443bf1b56	backend/local: allow nil modules (no config) if executing a plan	9 years ago
Mitchell Hashimoto	1480d0c5b8	backend/local: check for empty config on apply ... This prevents Terraform from crashing on apply/destroy with a directory with no Terraform configuration files. We allow a destroy with no files but not an apply.	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	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	f2e496a14c	Have backend operations properly unlock state ... Make sure unlock is called with the correct LockID during operations	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	cd233fef6a	make consul client pass state.Locker tests	9 years ago
James Bardin	67dc16c9ca	Make backend/local test pass	9 years ago
Mitchell Hashimoto	235b7eb38e	Merge pull request #11944 from hashicorp/f-state-slow ... show message if state lock acquisition/release is slow	9 years ago
Mitchell Hashimoto	5e4f6cf2b1	backend/local: fix could not to did not to prevent error look	9 years ago
Mitchell Hashimoto	65982bd412	backend/local: use new command/state package for better UX	9 years ago
James Bardin	80fab23e04	Don't test consul using demo.consul.io ... We shoudn't require an external service for unit test. TODO: create some proper acceptance tests for consul	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	54cac349a3	Add state locking to consul backend ... Use consul locks to implement state locking. The lock path is state path + "/.lock" which matches the consul cli default for locks. Lockinfo is stored at path + "/.lockinfo".	9 years ago
Mitchell Hashimoto	bdca9bffe4	backend/local: output warnings ... Fixes #11628 This is a simple fix to output warnings. I originally forgot to do this since the local backend didn't have a CLI UI at the time. It does now so this is an easy fix.	9 years ago
James Bardin	0d7752b0f5	Update runningOp.Err with State.Unlock error ... Have the defer'ed State.Unlock call append any error to the RunningOperation.Err field. Local error would be rare and self-correcting, but when the backend.Local is using a remote state the error may require user intervention.	9 years ago
James Bardin	9cdba1f199	enable local state locking for apply ... Have the LocalBackend lock the state during operations, and enble this for the apply comand.	9 years ago
Mitchell Hashimoto	a424203ea3	backend/local: validate module exists for plan ... Fixes #11504 The local backend should error if `terraform plan` is called in a directory with no Terraform config files (same behavior as 0.8.x). **New behavior:** We now allow `terraform plan -destroy` with no configuration files since that seems reasonable.	9 years ago
Mitchell Hashimoto	31f7cca77f	backend/local: fix crash (in tests) due to not guarding nil CLI	9 years ago
Mitchell Hashimoto	1f5d425428	backend/remote-state ... This allows migration of the remote state implementations to a richer experience including input asking.	9 years ago
Mitchell Hashimoto	13c34b16e8	backend/legacy ... This allows using legacy remote state backends with the new backend interface.	9 years ago
Mitchell Hashimoto	397e1b3132	backend/local ... The local backend implementation is an implementation of backend.Enhanced that recreates all the behavior of the CLI but through the backend interface.	9 years ago
Mitchell Hashimoto	8a070ddef0	backend: introduce the backend set of interfaces ... Backends are a mechanism that allow abstracting the behavior of Terraform CLI from the actual core. This allows us to slip in special behavior such as state loading, remote operations, etc.	9 years ago