16 Commits (f1db0fcf9bf4ebe523fff91302fbd080bca41603)

Author	SHA1	Message	Date
Mitchell Hashimoto	03493f7d46	command: validate backend config ... The validation itself was added a couple weeks ago but I forgot to actually call it. :sad:	9 years ago
Mitchell Hashimoto	1e3d452613	command: multistate to multistate conversions	9 years ago
Mitchell Hashimoto	c82d7dd56c	command: multi-state (non-default env) to single state	9 years ago
Mitchell Hashimoto	e75b666591	command: test multi-state to single state	9 years ago
Mitchell Hashimoto	3ef82e6b5f	command: test multi-state with default only to single state	9 years ago
Mitchell Hashimoto	1d8b76c89d	command: initial work on migrating envs, basic cases first	9 years ago
James Bardin	b53704ed87	Thread the environment through all commands ... Add Env and SetEnv methods to command.Meta to retrieve the current environment name inside any command. Make sure all calls to Backend.State contain an environment name, and make the package compile against the update backend package.	9 years ago
Mitchell Hashimoto	ebb22d3ecd	backend/local: don't RefreshState on State API	9 years ago
James Bardin	0c1b138719	Add state locking during backend init ... During backend initialization, especially during a migration, there is a chance that an existing state could be overwritten. Attempt to get a locks when writing the new state. It would be nice to always have a lock when reading the states, but the recursive structure of the Meta.Backend config functions makes that quite complex.	9 years ago
James Bardin	94f2f4d6ae	Create state files first for backup tests ... Previously when runnign a plan with no exitsing state, the plan would be written out and then backed up on the next WriteState by another BackupState instance. Since we now maintain a single State instance thoughout an operation, the backup happens before any state exists so no backup file is created. This is OK, as the backup state the tests were checking for is from the plan file, which already exists separate from the state.	9 years ago
James Bardin	1380bbedb2	don't print err in Fatalf when it's nil	9 years ago
James Bardin	b8bd4846db	fix test despite original comments ... Original comments were incorrect, and the test was checking for the absence of state	9 years ago
James Bardin	39ca4fa2f8	Ensure that backend tests check for data in state ... Test should not simply check for the existence of a file for state, but make sure that file also contains data.	9 years ago
James Bardin	8f7f1917f2	Remove state file data when writing a nil state ... The old behavior in this situation was to simply delete the file. Since we now have a lock on this file we don't want to close or delete it, so instead truncate the file at offset 0. Fix a number of related tests	9 years ago
James Bardin	eb59b5925e	Fix some tests, and make rest fail with good errs ... Having the state files always created for locking breaks a lot of tests. Most can be fixed by simple checking for state within a file, but a few still might be writing state when they shouldn't.	9 years ago
Mitchell Hashimoto	9654387771	command: meta.Backend is used for initializing the backend ... This is a complex function that handles all the potential cases that can happen with legacy remote state, new configurations, etc.	9 years ago