290 Commits (be543414ec00c743375fa78dabc087b8dc38eb82)

Author	SHA1	Message	Date
stack72	df9b2913ae	backend/manta: Add support for manta backend tiered path structure ... This was already added to triton-go and is now making its way to the manta backend ``` % acctests backend/remote-state/manta === RUN TestBackend_impl --- PASS: TestBackend_impl (0.00s) === RUN TestBackend --- PASS: TestBackend (27.36s) === RUN TestBackendLocked --- PASS: TestBackendLocked (16.24s) === RUN TestRemoteClient_impl --- PASS: TestRemoteClient_impl (0.00s) === RUN TestRemoteClient --- PASS: TestRemoteClient (3.40s) === RUN TestRemoteClientLocks --- PASS: TestRemoteClientLocks (7.17s) PASS ok github.com/hashicorp/terraform/backend/remote-state/manta ```	8 years ago
James Bardin	28c46d1a90	cleanup temp files from backend tests	8 years ago
stack72	a6f76aa0af	backend/manta: Manta Backend was not dealing with a ResourceNotFound ... Fixes: #17314 We now deal correctly with the creation of the state file - we were not dealing well with a ResourceNotFound error Now that this has been changed around, we try and create the statefile and if there is an error, we look for an existing statefile - previously this was not the order of operations	8 years ago
Martin Atkins	6aefa5835c	Merge #17218: Add -auto-approve to "terraform destroy" for consistency	8 years ago
Paul Tyng	c868092d2d	Standardize http.Client creation with User-Agent	8 years ago
James Bardin	e9a76808df	create clistate.Locker interface ... Simplify the use of clistate.Lock by creating a clistate.Locker instance, which stores the context of locking a state, to allow unlock to be called without knowledge of how the state was locked. This alows the backend code to bring the needed UI methods to the point where the state is locked, and still unlock the state from an outer scope. Provide a NoopLocker as well, so that callers can always call Unlock without verifying the status of the lock. Add the StateLocker field to the backend.Operation, so that the state lock can be carried between the different function scopes of the backend code. This will allow the backend context to lock the state before it's read, while allowing the different operations to unlock the state when they complete.	8 years ago
James Bardin	8242c773b8	missed the local state backend	8 years ago
James Bardin	57cbcbe99d	update remote state tests to use new test helpers	8 years ago
James Bardin	112c37458f	report the proper lock id from a state lock error ... Fix the now failing state unlock test by reporting the correct ID. The ID used by GCS is the generation number of the info object, which isn't known until the info is already written out. While we can't get the correct ID from the info data for the error rmessage, we can update it with the generation number after it's read.	8 years ago
James Bardin	1fee5ae172	update gcs to use the new backend tests	8 years ago
James Bardin	85d6b1d9cc	add test for lock error and force-unlock ... This adds a general test to verify that a remote state backend returns the expected error type when it cannot lock a state. It then extracts the ID reported in the error, and attempts to unlock the state using that ID, which simulated the force-unlock scenario. This is a separate test, since not all backends have persistent locks that can be unlocked later. We also split out the backend test to be called individually as needed.	8 years ago
James Bardin	ef8ed1e275	coalesce the backened interrupt code ... Moves the nested select statements for backend operations into a single function. The only difference in this part was that apply called PersistState, which should be harmless regardless of the type of operation being run.	8 years ago
James Bardin	7cba68326a	always wait for a RunningOperation to return ... If the user wishes to interrupt the running operation, only the first interrupt was communicated to the operation by canceling the provided context. A second interrupt would start the shutdown process, but not communicate this to the running operation. This order of event could cause partial writes of state. What would happen is that once the command returns, the plugin system would stop the provider processes. Once the provider processes dies, all pending Eval operations would return return with an error, and quickly cause the operation to complete. Since the backend code didn't know that the process was shutting down imminently, it would continue by attempting to write out the last known state. Under the right conditions, the process would exit part way through the writing of the state file. Add Stop and Cancel CancelFuncs to the RunningOperation, to allow it to easily differentiate between the two signals. The backend will then be able to detect a shutdown and abort more gracefully. In order to ensure that the backend is not in the process of writing the state out, the command will always attempt to wait for the process to complete after cancellation.	8 years ago
Laura Martin	6e1e614a56	Change -force to -auto-approve when destroying ... Since an early version of Terraform, the `destroy` command has always had the `-force` flag to allow an auto approval of the interactive prompt. 0.11 introduced `-auto-approve` as default to `false` when using the `apply` command. The `-auto-approve` flag was introduced to reduce ambiguity of it's function, but the `-force` flag was never updated for a destroy. People often use wrappers when automating commands in Terraform, and the inconsistency between `apply` and `destroy` means that additional logic must be added to the wrappers to do similar functions. Both commands are more or less able to run with similar syntax, and also heavily share their code. This commit updates the command in `destroy` to use the `-auto-approve` flag making working with the Terraform CLI a more consistent experience. We leave in `-force` in `destroy` for the time-being and flag it as deprecated to ensure a safe switchover period.	8 years ago
James Bardin	a5ed7d0ae4	Merge pull request #17086 from hashicorp/jbardin/GH-17083 ... only split the prefix string once from the s3 key	8 years ago
stack72	e9476c6765	backend/manta: Update manta dependencies ... Internally, triton-go has changed how it handles errors. We can now get rid of checking strings for errors, and we have introduced an errors library that wraps some of the major errors we encounter and test for	8 years ago
Masayuki Morita	f440dba137	Standardize on log level "WARN" rather than "WARNING"	8 years ago
James Bardin	43d000625d	only split the prefix string once from the s3 key ... Ensure that the prefix is only split off a single time when the workspace_key_prefix is a substring of the workspace or key name.	8 years ago
Stefan Schmidt	c200c170ad	Handle refresh errors.	8 years ago
Paddy	e4cdbd6c9f	Merge pull request #16936 from negz/gcskeys ... Support 'customer supplied encryption keys' in the GCS backend	8 years ago
James Bardin	7c703f2ab2	Merge pull request #16932 from rv-jmaggio/master ... Fixing issues with workspace_key_prefix for s3 backend	8 years ago
James Bardin	dd5882e5b2	Merge pull request #16992 from hashicorp/jbardin/go1.10-prep ... go1.10 prep	8 years ago
goraxe	fb6b349e58	backend/s3: Allow forcing use of the S3 path-style API ... This is useful when the underlying API is an S3-workalike service, rather than official S3.	8 years ago
Paul Stack	191cf283d5	backend/manta: Support Triton RBAC ... Triton Manta allows an account other than the main triton account to be used via RBAC. Here we expose the SDC_USER / TRITON_USER options to the backend so that a user can be specified.	8 years ago
James Bardin	4b49a323c3	go fmt ... slight change to go fmt coming in 0.10	8 years ago
rv-jmaggio	b313ce80c4	Changing prefix for empty workspace prefix	8 years ago
Henry Bell	56357c0ab7	Fix typo ('depracted' -> 'deprecated')	8 years ago
rv-jmaggio	bef64cfe91	Fixing implementation for empty string and making acceptance test work	8 years ago
rv-jmaggio	b02a1c8a46	clarifying tests and using SplitN in implementation	8 years ago
Nic Cope	011841124b	Support 'customer supplied encryption keys' in the GCS backend ... https://cloud.google.com/storage/docs/encryption#customer-supplied GCS state created using customer supplied encryption keys can only be read or modified using the same key.	8 years ago
rv-jmaggio	7f8d686074	refactor and add a test	8 years ago
rv-jmaggio	0889c118a8	Fixing issues with workspace_key_prefix	8 years ago
Rob Campbell	5daeee5f6d	Update various files for new version of "stringer" ... The latest version of stringer now uses strconv instead of fmt.	8 years ago
James Bardin	52eced589f	accept a path or contents for credentials ... Match the operation of the google provider, by accepting either a file path or contents for both `credentials` and `GOOGLE_CREDENTIALS`	8 years ago
James Bardin	2932203492	verify that a state can be read even when locked ... This should only happen when a state is loaded via the backend, as well as a remote state.	8 years ago
James Bardin	9dea2f78d4	create unique buckets for each test, and clean up ... This creates a unique bucket name for each test, so that the tests in parallel don't collide, and buckets left over from interrupted tests don't cause future failures. Also make sure that buckets are removed, regardless of content.	8 years ago
James Bardin	aec45e6967	backends should never create unmanaged resources ... The backend was creating bucket named in the configuration if it didn't exist. We don't allow other backends to do this, because these are not managed resources that terraform can control.	8 years ago
Kaveh Mousavi Zamani	7507e3cd21	backend/gcs: fix locking issue when used with terraform_remote_state ... Previously there was a problem with double-locking when using the GCS backend with the terraform_remote_state data source. Here we adjust the locking methodology to avoid that problem.	8 years ago
James Bardin	12b7dac124	Merge pull request #16833 from hashicorp/jbardin/plan-shutdown ... Fully enable shutdown for plan and refresh in the local backend	8 years ago
Sander van Harmelen	aaedf255c3	backend/s3: allow skipping the region check (#16757) ... Without the possibility to skip this check, it’s not possible to use a custom region with a third-party service that mimicks the S3 API.	8 years ago
James Bardin	85295e5c23	watch for cancellation in plan and refresh ... Cancellation in the local backend was only implemented for apply.	8 years ago
Martin Atkins	ba0514106a	return tfdiags.Diagnostics from validation methods ... Validation is the best time to return detailed diagnostics to the user since we're much more likely to have source location information, etc than we are in later operations. This change doesn't actually add any detail to the messages yet, but it changes the interface so that we can gradually introduce more detailed diagnostics over time. While here there are some minor adjustments to some of the messages to improve their consistency with terminology we use elsewhere.	9 years ago
James Bardin	00b7715710	Merge pull request #16586 from hashicorp/jbardin/providers ... Store resolved providers in state	9 years ago
Nic Cope	27ba7de77d	backend/gcs: automatically add trailing slash to prefix ... The backend doesn't function correctly if a trailing slash is not present, due to how workspaces are enumerated.	9 years ago
James Bardin	09180a10ff	cannot destroy without a config	9 years ago
James Bardin	d62e9217ae	update test state strings for backend/local	9 years ago
Malik Bougacha	ed0d57d1b7	Get the enviroment from the environment variable (#16326) ... * Get the enviroment from the enviroment variable * typo	9 years ago
stack72	1fd0f803e4	Migrate Manta Remote state to be a backend ... This PR changes manta from being a legacy remote state client to a new backend type. This also includes creating a simple lock within manta This PR also unifies the way the triton client is configured (the schema) and also uses the same env vars to set the backend up It is important to note that if the remote state path does not exist, then the backend will create that path. This means the user doesn't need to fall into a chicken and egg situation of creating the directory in advance before interacting with it	9 years ago
James Bardin	cf54ca3b0f	update tests for new consul packages ... Reuse the running consul server for all tests. Update the lostLockConnection package, since the api client should no longer lose a lock immediately on network errors.	9 years ago
James Bardin	3a03d3683e	update consul api packages ... This is from a commit just after the v1.0.0 release, because it removes the Porter service dependency for tests. The client api package was not changed.	9 years ago