7817 Commits (602b59cdc40c6fb0fd70817e2586cdc2db58b907)

Author	SHA1	Message	Date
Martin Atkins	5782357c28	backend: Update interface and implementations for new config loader ... The new config loader requires some steps to happen in a different order, particularly in regard to knowing the schema in order to decode the configuration. Here we lean directly on the configschema package, rather than on helper/schema.Backend as before, because it's generally sufficient for our needs here and this prepares us for the helper/schema package later moving out into its own repository to seed a "plugin SDK".	7 years ago
Sander van Harmelen	56e6c60f76	Merge pull request #18533 from alice-sawatzky/master ... change chef linux provisioner to use user:group chown syntax	7 years ago
Sean Chittenden	d749420a25	Fix drift caused from gofmt when running make dev and go 1.11. ... A fresh checkout of `origin/master` does not build atm using the `dev` target because `master` has not been formatted using `gofmt` from Go 1.11 (tis has been the case for a while if you've been running devel). None of the drift in question is especially new but now that Go 1.11 has been released and gofmt's formatting guidelines have been updated, it would be *really* nice if the code in `master` reflected the current tooling in order to avoid having to fight this drift locally. * 8mo: https://github.com/hashicorp/terraform/blame/master/backend/remote-state/s3/backend_test.go#L260-L261 * 6mo: https://github.com/hashicorp/terraform/blame/master/builtin/provisioners/chef/linux_provisioner_test.go#L124 * 1yr: 7cfeffe36b/command/init.go (L75-L76) * 12d: 7cfeffe36b/command/meta_backend_test.go (L1437) * 2yr: 7cfeffe36b/helper/schema/resource_timeout_test.go (L26) * 4yr: 7cfeffe36b/helper/schema/schema_test.go (L2059) * 1yr: 7cfeffe36b/plugin/discovery/get_test.go (L151)	8 years ago
Sander van Harmelen	3e935c846f	terraform/terraform_remote_state: accept complex configs ... The `remote` backend config contains an attribute that is defined as a `*schema.Set`, but currently only `string` values are accepted as the `config` attribute is defined as a `schema.TypeMap`. Additionally the `b.Validate()` method wasn’t called to prevent a possible panic in case of unexpected configurations being passed to `b.Configure()`. This commit is a bit of a hack to be able to support this in the 0.11 series. The 0.12 series will have proper support, so when merging 0.12 this should be reverted again.	8 years ago
Sander van Harmelen	7fb2d1b8de	Implement the Enterprise enhanced remote backend	8 years ago
Sander van Harmelen	97d1c46602	Update the backend import names ... It’s a purely cosmetic change, but I find it easier to read them like this.	8 years ago
Alice Sawatzky	15c65f981b	change chef linux provisioner to use user:group chown syntax	8 years ago
Skyler Layne	d1124a4e3d	Update resource_provisioner.go ... fix spacing for service url.	8 years ago
Andre Bindewald	de43f01d65	provisioner/local-exec: Support custom environment variables on Windows ... Due to an incorrect slice allocation, the environment variable list was created with an empty string element for each real element added. It appears that this was silently ignored on Unix, but caused the following environment settings to be ignored altogether on Windows.	8 years ago
James Bardin	f8b691f743	Merge pull request #17781 from hashicorp/jbardin/habitat ... `enable` habitat supervisor service before `start`	8 years ago
James Bardin	c1edaadc7b	Merge pull request #17403 from rwc/hab-provisioner-updates ... [provisioner-habitat] Fix package channel honoring and documentation	8 years ago
Marko Springfeldt	a201b04b26	`enable` habitat supervisor service before `start` ... Signed-off-by: Arash Zandi <arash.zandi@smartb.eu>	8 years ago
James Bardin	e9e4ee4940	Merge pull request #17609 from hashicorp/jbardin/remote-command ... clean up remote.Cmd api	8 years ago
James Bardin	ad8642e2c2	have remote.ExitError format errors and status ... Since all use cases of ExitStatus are just putting it into fmt.Errorf, usually with the command string, have ExitStatus do that for the caller.	8 years ago
James Bardin	56acda00bc	add timeout test to remote-exec ... Add a test to remote-exec to make sure the proper timeout is honored during apply. TODO: we need some test helpers for provisioners, so they can all be verified.	8 years ago
James Bardin	9b4b5f2a72	use correct context for communicator.Retry ... The timeout for a provisioner is expected to only apply to the initial connection. Keep the context for the communicator.Retry separate from the global cancellation context.	8 years ago
Scott Hain	07aeea51da	Updates the chef provisioner to allow specifying a channel (#17355) ... * Updates the chef provisioner to allow specifying a channel This also updates the omnitruck url to the current url. Signed-off-by: Scott Hain <shain@chef.io> * Update omnitruck URL Signed-off-by: Scott Hain <shain@chef.io>	8 years ago
James Bardin	3fbdee0777	clean up remote.Cmd api ... Combine the ExitStatus and Err values from remote.Cmd into an error returned by Wait, better matching the behavior of the os/exec package. Non-zero exit codes are returned from Wait as a remote.ExitError. Communicator related errors are returned directly. Clean up all the error handling in the provisioners using a communicator. Also remove the extra copyOutput synchronization that was copied from package to package.	8 years ago
James Bardin	a1061ed931	update the chef and habitat error handling ... Use the new ExitStatus method, and also check the cmd.Err() method for errors. Remove leaks from the output goroutines in both provisioners by deferring their cleanup, and returning early on all error conditions.	8 years ago
James Bardin	a715430d24	fix exit status handling in salt-masterless ... Convert to the new Cmd.ExitStatus() method in the salt-masterless provisioner. Add calls to Wait and remove race conditions around setting the status.	8 years ago
James Bardin	af132a186d	remove timeout from remote-exec command context ... The timeout for the remote command was taken from the wrong config field, and the connection timeout was being used which is 5 min. Any remote command taking more than 5 min would be terminated by disconnecting the communicator. Remove the timeout from the context, and rely on the global timeout provided by terraform. There was no way to get the error from the communicator previously, so the broken connection was silently ignored and the provisioner returned successfully. Now we can use the new cmd.Err() method to retrieve any errors encountered during execution.	8 years ago
James Bardin	e011dd95f3	don't let default workspace override environment ... The workspace attribute should only override the environment if it's not the default value.	8 years ago
James Bardin	13433687cb	filter null output values from state ... While null values should not normally appear in a state file, we should filter the values rather than crash.	8 years ago
Kristiyan Nikolov	999f9096c1	provisioner/local-exec: Allow passing environment variables	8 years ago
Paweł Socha	be8d39210d	Wait for ssh connection	8 years ago
Paweł Socha	627bb24ea6	fix ssh problem with communicator.Retry	8 years ago
Rob Campbell	bbd3d7f7a2	Updates the capitalization of the bind documenation for habitat ... provisioner. Also fixes an issue where channels and URLs are not honored in the initial package install. Signed-off-by: Rob Campbell <rcampbell@chef.io>	8 years ago
chrisjob1021	10bb21e9c4	provisioner/local-exec: Optional "working_dir" argument ... This new argument allows overriding of the working directory of the child process, with the default still being the working directory of Terraform itself.	8 years ago
James Bardin	0345d960b2	simplify remote-exec runScripts ... There no reason to retry around the execution of remote scripts. We've already established a connection, so the only that could happen here is to continually retry uploading or executing a script that can't succeed. This also simplifies the streaming output from the command, which doesn't need such explicit synchronization. Closing the output pipes is sufficient to stop the copyOutput functions, and they don't close around any values that are accessed again after the command executes.	8 years ago
James Bardin	c1b35ad69b	have the ssh communicator return fatal errors ... This will let the retry loop abort when there are errors which aren't going to ever be corrected.	8 years ago
James Bardin	e331ae9842	remove retryFunc ... it's now in the communicator package	8 years ago
James Bardin	d02250c2b9	remove retryFunc ... it's now in the communicator package	8 years ago
James Bardin	89a0ac6e89	remove retryFunc ... It's now in the communicator package	8 years ago
James Bardin	f5b8091e2c	remove retryFunc ... It's now in the communicator package	8 years ago
Nolan Davidson	f43e592849	[provisioner-habitat] Detect if hab user exists (#17195) ... Currently the provisioner will fail if the `hab` user already exists on the target system. This adds a check to see if we need to create the user before trying to add it. Fixes #17159 Signed-off-by: Nolan Davidson <ndavidson@chef.io>	8 years ago
Nolan Davidson	848375b9a6	[provisioner-habitat] Allow custom service name (#17196) ... This change allows the Habitat supervisor service name to be configurable. Currently it is hard coded to `hab-supervisor`. Signed-off-by: Nolan Davidson <ndavidson@chef.io>	8 years ago
Jeremiah Snapp	7595e27772	Fix chef provisioner validateFn ... Correctly validate Chef provisioner's `use_policyfile` field even if its value is a string type. Signed-off-by: Jeremiah Snapp <jeremiah@chef.io>	8 years ago
Masayuki Morita	f440dba137	Standardize on log level "WARN" rather than "WARNING"	8 years ago
James Bardin	4b49a323c3	go fmt ... slight change to go fmt coming in 0.10	8 years ago
Rob Campbell	29f70bc112	Adds build_auth_token to Habitat Provisioner ... First successful run with private origin and HAB_AUTH_TOKEN set Update struct, schema, and decodeConfig names to more sensible versions Cleaned up formatting Update habitat provisioner docs Remove unused unitstring	8 years ago
Nolan Davidson	a50a383946	Additional work on the habitat provisioner. ... Signed-off-by: Nolan Davidson <ndavidson@chef.io>	8 years ago
Nolan Davidson	653db95df7	Initial implementation of a habitat provisioner ... First pass at loading the config data using the TF schema. Signed-off-by: Nolan Davidson <ndavidson@chef.io>	8 years ago
Nic Cope	5c58ef16f7	provider/terraform: deprecate "environment" in favor of "workspace"	8 years ago
Subba Rao Pasupuleti	44cb98e04f	provisioner/salt-masterless: Wait for operations to complete ... Previously the provisioner did not wait until the Salt operation had completed before returning, causing some operations not to be applied, and causing the output to get swallowed. Now we wait until the remote work is complete, and copy output into the Terraform log in a similar way as is done for other provisioners.	8 years ago
Radek Simko	2974d63e75	Merge pull request #16588 from hashicorp/f-panic-on-invalid-rd-set ... helper/schema: Opt-in panic on invalid ResourceData.Set	8 years ago
Radek Simko	e93d64b18c	helper/schema: Opt-in panic on invalid ResourceData.Set	8 years ago
Martin Atkins	bcc5dffea2	provider/terraform: import terraform provider back into core	8 years ago
Martin Atkins	a3ced1a367	provider/terraform: reorganize for merge into core ... The "terraform" provider was previously split out into its own repository, but that turned out to be a mistake due to how tightly it depends on aspects of Terraform Core. Here we prepare to bring it back into the core repository by reorganizing the directory layout to conform with what's expected there.	8 years ago
Chris Marchesi	5d5a670d69	provider/test: Added complex-ish list testing ... Added a list SetNew test to try and reproduce issues testing diff customization with the Nomad provider. We are running into "diffs didn't match during apply", with the plan diff exhibiting a strange off-by-one-type error in a list diff: datacenters.#: "1" => "2" datacenters.0: "dc1" => "dc2" datacenters.1: "" => "dc3" datacenters.2: "" => "dc3" The test here does not reproduce that issue, unfortunately, but should help pinpoint the root cause through elimination.	8 years ago
Chris Marchesi	529d7e6dae	helper/schema: Review -> CustomizeDiff ... Restoring the naming of this field in the resource back to CustomizeDiff, as this is generally more descriptive of the process that's happening, despite the lengthy name.	8 years ago