166 Commits (e3785e1bcbb4f5259c3bc8114cc4d2c60ab86e6b)

Author	SHA1	Message	Date
Loïc Albertin	21b287e919	backend/consul: allow specifying various Consul client security options ... These new options are equivalent to the consul CLI arguments -ca-file, -client-cert and -client-key.	9 years ago
James Bardin	5d50e764ea	deprecate the "azure" backend name ... Alert users to use the current "azurerm" naming.	9 years ago
James Bardin	0e873d70ed	Merge pull request #15840 from hashicorp/jbardin/deprecate-backend ... add the ability to mark a backend as deprecated	9 years ago
James Bardin	cc454fcc56	add the ability to mark a backend as deprecated ... This is a simple wrapper to allow a backend to be marked as deprecated during initialization.	9 years ago
Peter McAtominey	b74b26bcfa	backend: alias azurerm to azure	9 years ago
Peter McAtominey	6b9b5ec297	backend/azure: update to latest SDK	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
James Bardin	2bb5007690	Merge pull request #15683 from hashicorp/jbardin/remote-state-lineage ... Remove strict lineage check in remote.State	9 years ago
James Bardin	4c7cd549cd	don't allow leading slashes in s3 remote state key ... S3 accepts objects with a leading slash and strips them off. This works fine except in our workspace hierarchy, which then can no longer find suffixes matching the full key name.	9 years ago
James Bardin	dc30761497	Merge pull request #15567 from hashicorp/jbardin/consul-update ... Update consul vendor and remote state	9 years ago
James Bardin	c3e943bed2	add another failing test for remote.State lineage ... Want to make sure we don't hit this again.	9 years ago
James Bardin	18d71f273e	make inmem behave more like remote backends ... When remote backend imeplemtations create a new named state, they may need to acquire a lock and/or save an actual empty state to the backend. Copy this behavior in the inmem backend for testing.	9 years ago
James Bardin	5deef9621d	export Reset() ... This package is used for testing, so there needs to be an easy method for reinitializing the stored data between tests.	9 years ago
James Bardin	ac60ddcd40	Support named states in inmeme backend ... Used to expand test coverage	9 years ago
James Bardin	1070d04b07	Remove consul context adapter for RenewPeriodic ... Updated the vendored consul which no longer requires the channel adapter to convert a `chan stuct{}` to a `<-chan struct{}`. Call testutil.NewTestServerConfigT with the new signature.	9 years ago
James Bardin	9a7ffbfb1b	Merge pull request #15566 from hashicorp/jbardin/state-serial ... Add warning to mismatched plan state	9 years ago
James Bardin	dd9a54c661	Merge pull request #15435 from hashicorp/jbardin/state-path-message ... only show state path help if state is local	9 years ago
James Bardin	50f412bff4	Merge pull request #15557 from hashicorp/jbardin/consul-lock-sessions ... have the consul client manage the lock session	9 years ago
James Bardin	a1727ec4c2	Add warning to mismatched plan state ... Forward-port the plan state check from the 0.9 series. 0.10 has improved the serial handling for the state, so this adds relevant comments and some more test coverage for the case of an incrementing serial during apply.	9 years ago
James Bardin	bcb11f6d89	have the consul client manage the lock session ... When a consul lock is lost, there is a possibility that the associated session is still active. Most commonly, the long request to watch the lock key may error out, while the session is continually refreshed at a rate of TTL/2. First have the lock monitor retry the lock internally for at least 10 seconds (5 attempts with the default 2 second wait time). In most cases this will reconnect on the first try, keeping the lock channel open. If the consul lock can't recover itself, then cancel the session as soon as possible (terminating the PreiodicRenew will call Session.Destroy), and start over. In the worse case, the consul agents were split, and the session still exists on the leader so we may need to wait for the old session TTL, plus the LockWait time to renew the lock. We use a Context for the cancellation channels here, because that removes the need to worry about double-closes and nil channels. It requires an awkward adapter goroutine for now to convert the Done() `<-chan` to a `chan` for PeriodicRenew, but makes the rest of the code safer in the long run.	9 years ago
James Bardin	193d4b868c	backend state tests must honor lineage ... Remote state implementations may initialize a lineage when creating a new named state (i.e. "workspace"). The tests were ignoring that initial lineage to write a new state to the backend.	9 years ago
James Bardin	3fb76f3ebb	only show state path help if state is local	9 years ago
James Bardin	5066fa2151	Merge pull request #13871 from fatmcgav/swift_move_to_backend ... Move Swift remote state to backend	9 years ago
Martin Atkins	6afa72f6ca	command: minor adjustments to the -auto-approve=false UX ... Some tweaks to the messaging and presentation.	9 years ago
David Glasser	14af879fe0	command: also print plan for destroy	9 years ago
David Glasser	039d36bf91	command: add "apply -auto-approve=false" flag ... A common reason to want to use `terraform plan` is to have a chance to review and confirm a plan before running it. If in fact that is the only reason you are running plan, this new `terraform apply -auto-approve=false` flag provides an easier alternative to P=$(mktemp -t plan) terraform refresh terraform plan -refresh=false -out=$P terraform apply $P rm $P The flag defaults to true for now, but in a future version of Terraform it will default to false.	9 years ago
Martin Atkins	45a4ba1ea7	Merge #15344: Avoid double-counting resources to create	9 years ago
James Bardin	42cbb716b7	Merge pull request #15370 from rowleyaj/s3_backend_workspaces ... Add configurable workspace prefix for S3 Backend	9 years ago
Alex Rowley	2dd464cf8f	Clarify field description	9 years ago
Chris Marchesi	5654a676d9	core: Skip diff hooks for stubs on eval altogether ... Rather than overloading InstanceDiff with a "Stub" attribute that is going to be largely meaningless, we are just going to skip pre/post-diff hooks altogether. This is under the notion that we will eventually not need to "stub" a diff for scale-out, stateless nodes on refresh at all, so diff behaviour won't be necessary at that point, so we should not assume that hooks will run at this stage anyway. Also as part of this removed the CountHook test that is now failing because CountHook is out of scope of the new behaviour.	9 years ago
Chris Marchesi	50cd33f781	core: Move Refreh/Plan diff count to general operation test ... We are changing the behaviour of the "stub" diff operation to just have the pre/post-diff hooks skipped on eval, meaning that the test against CountHook will ultimately be meaningless and fail, hence we need a different test here that tests it on a more general level.	9 years ago
James Bardin	1fa7667ad4	s3 backend should use Client.Delete to DeleteState ... The s3.Backend was using it's own code for DeleteState, but the dynamo entries are only handled through the RemoteClient. Have DeleteState use a RemoteClient for delete.	9 years ago
James Bardin	ebf4413e95	add named named state delete+create-delete test ... This ensures that we don't leave any conflicting state artifacts preventing the recreation of a named state.	9 years ago
James Bardin	ac937a890d	improve plugin reinit error text	9 years ago
James Bardin	7a955f990c	make display plugin checksum error to user ... The error follows a generic message, so can be ignored by users who may not understand the implications.	9 years ago
Alex Rowley	db40dc06ab	Add configurable workspace prefix for S3 Backend ... Fixes #13184	9 years ago
James Bardin	5be15ed77c	have the local backend provide a plugin init msg ... During plan and apply, because the provider constraints need to be built from a plan, they are not checked until the terraform.Context is created. Since the context is always requested by the backend during the Operation, the backend needs to be responsible for generating contextual error messages for the user. Instead of formatting the ResolveProviders errors during NewContext, return a special error type, ResourceProviderError to signal that init will be required. The backend can then extract and format the errors.	9 years ago
Chris Marchesi	f249386c8a	core: Test to ensure PostDiff is ignoring stubs ... Added a test that shows that PostDiff is ignoring diffs where the Stub attribute is set.	9 years ago
Chris Marchesi	45528b2217	core: Instance/EvalDiff.Quiet -> Stub ... Changed the language of this field to indicate that this diff is not a "real" diff, in that it should not be acted on, versus a "quiet" mode, which would indicate just simply to act silently.	9 years ago
Chris Marchesi	eef933f2a7	core: Don't count scaled-out resources twice in the UI ... This fixes a bug with the new refresh graph behaviour where a resource was being counted twice in the UI on part of being scaled out: * We are no longer transforming refresh nodes without state to plannable resources (the transformer will be removed shortly) * A Quiet flag has been added to EvalDiff and InstanceDiff - this allows for the flagging of a diff that should not be treated as real diff for purposes of planning * When there is no state for a refresh node now, a new path is taken that is similar to plan, but flags Quiet, and does nothing with the diff afterwards. Tests pending - light testing has confirmed this should fix the double count issue, but we should have some tests to actually confirm the bug.	9 years ago
Gavin Williams	c2550e78cf	Rename openstack provider for swift remote backend	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	ac959af6b4	rename aws provider import in s3 backend	9 years ago
Martin Atkins	f7ce6a15f8	backend: Operation.Environment renamed to "Workspace" ... This is part of an effort to switch this terminology across all of Terraform.	9 years ago
Martin Atkins	418a8a8bc9	command + backend: rename various API objects to "Workspace" terminology ... We're shifting terminology from "environment" to "workspace". This takes care of some of the main internal API surface that was using the old terminology, though is not intended to be entirely comprehensive and is mainly just to minimize the amount of confusion for maintainers as we continue moving towards eliminating the old terminology.	9 years ago
Martin Atkins	5026e1d313	backend/local: "environment_dir" renamed to "workspace_dir" ... As part of switching our terminology, we begin a deprecation cycle for "environment_dir" and advise users to switch to "workspace_dir" instead.	9 years ago
David Glasser	c25d848ffb	core: allow overriding environment name via env var ... This allows you to run multiple concurrent terraform operations against different environments from the same source directory. Fixes #14447. Also removes some dead code which appears to do the same thing as the function I modified.	9 years ago
Martin Atkins	c835ef8ff3	Update tests for the new ProviderResolver interface ... Rather than providing an already-resolved map of plugins to core, we now provide a "provider resolver" which knows how to resolve a set of provider dependencies, to be determined later, and produce that map. This requires the context to be instantiated in a different way, so this very noisy diff is a mostly-mechanical update of all of the existing places where contexts get created for testing, using some adapted versions of the pre-existing utilities for passing in mock providers.	9 years ago
Martin Atkins	a42ebe389c	Revert "have StateHook periodically PersistState" ... This reverts commit b73d037761. This commit seems to have introduced a race condition where we can concurrently keep updating state after we've checked if we need to increase the serial, and thus end up writing partial changes to the state backend. In the case of Terraform Enterprise, this fails altogether because of the state hash consistency check it does.	9 years ago
Radek Simko	1244309579	Fix stringer comments (#15069)	9 years ago