698 Commits (eaac9fbca3aebd1d1f23ff2b70089739872b166a)

Author	SHA1	Message	Date
Martin Atkins	b1763e262a	Restore stringer-generated files back to new version ... stringer has changed the boilerplate it generates in a recent version. We'd previously updated to the new format but accientally rolled back to the old while merging a long-running feature branch. This restores us back to the new format again.	9 years ago
Jasmin Gacic	61499cfcf0	Provider Oneandone (#13633) ... * Terraform Provider 1&1 * Addressing pull request remarks * Fixed imports * Fixing remarks * Test optimiziation	9 years ago
James Bardin	dca89519ec	Merge pull request #13825 from hashicorp/jbardin/reconfigure ... add init -reconfigure flag	9 years ago
James Bardin	0e0f0b64b9	add init -reconfigure test ... Check that we can reconfigure a backend ignoring the saved config, and without effecting the saved backend.	9 years ago
James Bardin	7aa2ce8341	add -reconfigure option for init ... The reconfigure flag will force init to ignore any saved backend state. This is useful when a user does not want any backend migration to happen, or if the saved configuration can't be loaded at all for some reason.	9 years ago
Jake Champlin	35388cbc31	Merge pull request #13468 from hashicorp/f-oracle-compute ... provider/opc: Add Oracle Compute Provider	9 years ago
Quentin Machu	bf8d932d23	provider/local: Implement a new local_file resource ... This commit adds the ability to provision files locally. This is useful for cases where TerraForm generates assets such as TLS certificates or templated documents that need to be saved locally. - While output variables can be used to return values to the user, it is not extremly suitable for large content or when many of these are generated, nor is it practical for operators to manually save them on disk. - While `local-exec` could be used with an `echo`, this provider works across platforms and do not require any convoluted escaping.	9 years ago
James Bardin	d1b4df42ed	missing PersistState in env new	9 years ago
David Joos	bbd2e6de35	Fix for minor typo ... "destionation" -> "destination"	9 years ago
tombuildsstuff	3a084b061a	Merge branch 'master' into f-oracle-merge	9 years ago
Jake Champlin	456d43e200	Merge remote-tracking branch 'origin/master' into f-oracle-compute	9 years ago
James Bardin	fb4a365d12	noop migrate copy, add -lock and -input ... A couple commits got rebased together here, and it's easier to enumerate them in a single commit. Skip copying of states during migration if they are the same state. This can happen when trying to reconfigure a backend's options, or if the state was manually transferred. This can fail unexpectedly with locking enabled. Honor the `-input` flag for all confirmations (the new test hit some more). Also unify where we reference the Meta.forceInitCopy and transfer the value to the existing backendMigrateOpts.force field.	9 years ago
James Bardin	aad143b6d1	set stateLock to true when building meta flagSet ... Any commands that use `stateLock` should have a flag to set that value, but set a failsafe to true just in case.	9 years ago
James Bardin	d059939f88	Merge pull request #13262 from hashicorp/jbardin/lock-timeouts ... lock timeouts	9 years ago
Radek Simko	fc72a20c66	command/hook_ui: Increase max length of state IDs (#13317)	9 years ago
Jake Champlin	edc524df55	provider/opc: Update OPC Provider ... Updates the OPC provider to a fully working version.	9 years ago
James Bardin	3d604851c2	test -lock-timeout from cli	9 years ago
James Bardin	5eca913b14	add cli flags for -lock-timeout ... Add the -lock-timeout flag to the appropriate commands. Add the -lock flag to `init` and `import` which were missing it. Set both stateLock and stateLockTimeout in Meta.flagsSet, and remove the extra references for clarity.	9 years ago
James Bardin	305ef43aa6	provide contexts to clistate.Lock calls ... Add fields required to create an appropriate context for all calls to clistate.Lock. Add missing checks for Meta.stateLock, where we would attempt to lock, even if locking should be skipped.	9 years ago
James Bardin	3f0dcd1308	Have the clistate Lock use LockWithContext ... - Have the ui Lock helper use state.LockWithContext. - Rename the message package to clistate, since that's how it's imported everywhere. - Use a more idiomatic placement of the Context in the LockWithContext args.	9 years ago
James Bardin	75458a182d	remove extra state.Locker assertions ... All states are lockers, so get rid of extra asertions.	9 years ago
James Bardin	8050eda52d	don't delete local state on a local backend ... Don't erase local state during backend migration if the new and old paths are the same. Skipping the confirmation and copy are handled in another patch, but the local state was always erased by default, even when it was our new state.	9 years ago
James Bardin	50023e9a60	honor `input=false` in state migration ... return an error when confirming a copy if -input=false	9 years ago
James Bardin	7d23e1ef20	add equivalent tests to meta_backend_test	9 years ago
James Bardin	c891ab50b7	detect when backend.Hash needs update ... It's possible to not change the backend config, but require updating the stored backend state by moving init options from the config file to the `-backend-config` flag. If the config is the same, but the hash doesn't match, update the stored state.	9 years ago
James Bardin	ff2d753062	add Rehash to terraform.BackendState ... This method mirrors that of config.Backend, so we can compare the configration of a backend read from a config vs that of a backend read from a state. This will prevent init from reinitializing when using `-backend-config` options that match the existing state.	9 years ago
Martin Atkins	76dca009e0	Allow escaped interpolation-like sequences in variable defaults ... The variable validator assumes that any AST node it gets from an interpolation walk is an indicator of an interpolation. Unfortunately, back in f223be15 we changed the interpolation walker to emit a LiteralNode as a way to signal that the result is a literal but not identical to the input due to escapes. The existence of this issue suggests a bit of a design smell in that the interpolation walker interface at first glance appears to skip over all literals, but it actually emits them in this one situation. In the long run we should perhaps think about whether the abstraction is right here, but this is a shallow, tactical change that fixes #13001.	9 years ago
Martin Atkins	21cd5595e2	Update stringer-generated files to new boilerplate ... golang/tools commit 23ca8a263 changed the format of the leading comment to comply with some new standards discussed here: https://golang.org/issue/13560 This is the result of running generate with the latest version of stringer. Everyone working on Terraform will need to update stringer after this is merged, to avoid reverting this: go get -u golang.org/x/tools/cmd/stringer	9 years ago
James Bardin	f172b4a023	Merge pull request #13105 from hashicorp/jbardin/command-env ... disallow env names that aren't url-safe	9 years ago
James Bardin	2cffa25235	Add test to verify that Validation isn't called ... The apply won't succeed because we don't have a valid plan, but this verifies that providing a plan file prevents Validation.	9 years ago
James Bardin	9d118325b3	Reject names that aren't url-safe ... Environment names can be used in a number of contexts, and should be properly escaped for safety. Since most state names are store in path structures, and often in a URL, use `url.PathEscape` to check for disallowed characters	9 years ago
James Bardin	8027fe9e08	Don't Validate if we have an execution plan ... The plan file should contain all data required to execute the apply operation. Validation requires interpolation, and the `file()` interpolation function may fail if the module files are not present. This is the case currently with how TFE executes plans.	9 years ago
James Bardin	54e536cfe0	add `-force-copy` option to init command ... The `-force-copy` option will suppress confirmation for copying state data. Modify some tests to use the option, making sure to leave coverage of the Input code path.	9 years ago
Mitchell Hashimoto	d01886a644	command: remove legacy remote state on migration ... Fixes #12871 We were forgetting to remove the legacy remote state from the actual state value when migrating. This only causes an issue when saving a plan since the plan contains the state itself and causes an error where both a backend + legacy state exist. If saved plans aren't used this causes no noticable issue. Due to buggy upgrades already existing in the wild, I also added code to clear the remote section if it exists in a standard unchanged backend	9 years ago
Mitchell Hashimoto	23505cc2a8	Merge pull request #12818 from hashicorp/b-legacy ... command: use backendinit instead of initializing legacy directly	9 years ago
James Bardin	434e78158a	Merge pull request #12812 from hashicorp/jbardin/hook-ui-race ... fix race in hook ui PreApply test	9 years ago
Mitchell Hashimoto	4f59576231	command: fix awkward wording in message	9 years ago
James Bardin	b9931c437d	fix race in hook ui PreApply test ... Fix a race in the PreApply test, and make the PreApply background task actually concealable.	9 years ago
Mitchell Hashimoto	96e38041ab	command: use backendinit instead of initializing legacy directly ... Fixes #12806 This should've been part of 2c19aa69d9 This is the same issue, just missed a spot. Tests are hard to cover for this since we're removing the legacy backends one by one, eventually it'll be gone. A good sign is that we don't import backendlegacy at all anymore in command/	9 years ago
Mitchell Hashimoto	c87f3dfdd5	command/init: add test for -backend-config k/v	9 years ago
Mitchell Hashimoto	df8529719c	command/init: backend-config accepts key=value pairs ... This augments backend-config to also accept key=value pairs. This should make Terraform easier to script rather than having to generate a JSON file. You must still specify the backend type as a minimal amount in configurations, example: ``` terraform { backend "consul" {} } ``` This is required because Terraform needs to be able to detect the _absense_ of that value for unsetting, if that is necessary at some point.	9 years ago
Mitchell Hashimoto	e1f4eca93c	command: apply needs to look at the right field for backend state ... Plans were properly encoding backend configuration but the apply was reading it from the wrong field. :( This meant that every apply from a plan was applying it locally with backends. This needs to get released ASAP.	9 years ago
Mitchell Hashimoto	25312c8985	command/push: update copy for remote state error	9 years ago
James Bardin	9bfa361e21	Merge pull request #12778 from hashicorp/jbardin/GH-12741 ... change to default state after backend migration	9 years ago
Mitchell Hashimoto	6921457601	Merge pull request #12777 from hashicorp/b-refresh-empty ... backend/local: allow refresh on empty/non-existent state	9 years ago
James Bardin	ea095eda87	change to default state after backend migration ... When migrating from a multi-state backend to a single-state backend, we have to ensure that our locally configured environment is changed back to "default", or we won't be able to access the new backend.	9 years ago
Mitchell Hashimoto	2be1f55cbb	backend/local: allow refresh on empty/non-existent state ... This allows a refresh on a non-existent or empty state file. We changed this in 0.9.0 to error which seemed reasonable but it turns out this complicates automation that runs refresh since it now needed to determine if the state file was empty before running. Its easier to just revert this into a warning with exit code zero. The reason this changed is because in 0.8.x and earlier, the output would be simply empty with exit code zero which seemed odd.	9 years ago
Mitchell Hashimoto	81639480fb	command: recompute config hash with ConfigFile set ... Fixes #12749 If we merge in an extra partial config we need to recompute the hash to compare with the old value to detect that change. This hash needs to NOT be stored and just used as a temporary. We want to keep the original hash in the state so that we don't detect a change from the config (since the config will always be partial).	9 years ago
Mitchell Hashimoto	87201ec854	command/push: test for push with new backends	9 years ago
Mitchell Hashimoto	8b208a597d	command/push: don't allow pushing with local backend	9 years ago