20082 Commits (eccfa6de5ca33867f83ea2ea950579c7a2bd4d9c)

 

All Branches   

Search

Author	SHA1	Message	Date
Martin Atkins	590bbe9b31	examples: Remove the consul example ... This is now in the consul provider repository, linked from the README here.	9 years ago
Martin Atkins	583c24a3c2	examples: Update README to reflect 0.10 init/apply workflow ... Previous instructions assumed the pre-0.9 version of init, which served a different purpose.	9 years ago
Martin Atkins	0e0c7883e4	examples: Remove the clc example ... This has now moved into the repository for the CenturyLink Cloud provider, linked from the README here.	9 years ago
Martin Atkins	3b95c85f18	examples: Remove the Google Cloud examples ... These are now in the provider's own repository, linked from the README here.	9 years ago
seph	29ebe07e1e	Update link to the AWS example	9 years ago
Jake Champlin	0c69e46649	Update CHANGELOG.md	9 years ago
Jake Champlin	f98cfc9018	Merge pull request #15617 from svanharmelen/b-chef-provisioner ... provisioner/chef: fix panic	9 years ago
protondonor	fc3782f051	Document failure behavior for `import` command. ... - Remove link to issue 11835.	9 years ago
protondonor	1069aab47a	Document changes to terraform import in the release notes. ... - Documentation based on the commit message for the change (9a398a7793)	9 years ago
Sander van Harmelen	b01f68f343	provisioner/chef: fix panic ... Fixes #15431 Fixes #15500	9 years ago
Martin Atkins	e079e9d339	examples: remove azure examples ... These have now moved into the AzureRM provider repository, linked from the README here.	9 years ago
Martin Atkins	9be103b62d	examples: Remove AliCloud and AWS examples ... The examples for these providers have moved into the providers' own repositories, so this is just cleaning up the old copies in the main repo to avoid any confusion caused by the duplication. The examples readme has links to these provider-specific examples so that people looking for them in the old location can still find them.	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	7584ac1247	update consul vendor	9 years ago
James Bardin	0bca383b6b	Merge pull request #15528 from alrs/command-swallowed-errors ... Fix swallowed errors in command package.	9 years ago
Lars Lehtonen	822a98a0b4	Fix swallowed tests in terraform package tests	9 years ago
Jake Champlin	c40be7cd14	Merge pull request #15598 from alrs/helper-swallowed-error ... Fix swallowed err in acctest package	9 years ago
Lars Lehtonen	e34f194b31	Fix swallowed err in acctest package	9 years ago
Lars Lehtonen	119996b815	Return immediately after newly-added error condition	9 years ago
Martin Atkins	8666d36609	Merge #15596: docker image build configurations	9 years ago
Martin Atkins	1fac5de738	release: clean up after v0.10.0-rc1	9 years ago
Martin Atkins	243951c70a	v0.10.0-rc1	9 years ago
Martin Atkins	2b3b62dab5	build: documentation for the new docker image release process ... At the time of commit this file contains some things that are not yet true due to the dockerhub configuration not having been updated. This therefore remains aspirational until merged, after which the docherhub configuration will be updated.	9 years ago
Martin Atkins	0f9af4dfa9	build: configuration for building "release" docker images ... These are different than our "full" images because they include a binary already released to releases.hashicorp.com, whereas the root Dockerfile directly builds from the current work tree. This particular Dockerfile is not intended to be run manually, but rather exists only to drive the dockerhub automated build.	9 years ago
Martin Atkins	909c45488f	build: Move the "full" Dockerfile into the root of our main repo ... Previously this lived in a separate repo docker-hub-images, shared with other products. Having multiple products sharing a repo complicates release processes and works against some assumptions made by the Dockerhub build system. The "full" Dockerfile contains a Terraform binary built from source, and so it can be used with any arbitrary Terraform source tree. This doesn't yet include the "light" Dockerfile, which instead makes an image from official binaries already on releases.hashicorp.com. That will follow in a subsequent commit.	9 years ago
James Bardin	cb5739f1a0	update CHANGELOG.md	9 years ago
Martin Atkins	f6dace3476	website: document the Checkpoint service and how to disable it ... This is documented for all other Hashicorp products using this service but was missed for Terraform. This serves as a disclosure of the fact that Terraform reaches out to a Hashicorp service, an explanation of the purpose of that request, and instructions on how to disable it in environments where it is inappropriate or cannot be supported due to a firewall or other connectivity restrictions.	9 years ago
Martin Atkins	da0aec1b32	website: attempt to clarify "terraform import" usage docs ... Based on feedback from #15569 that the previous example was too abstract and did not give enough context about what each of the different arguments mean and how they generalize to other resource types.	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
Martin Atkins	c57dbebe84	documentation: explain provider dev environment setup ... The intent here is just to introduce some initial docs on our recommended way to develop plugins in the same GOPATH as Terraform itself. The documentation in this area needs some more fundamental rework as it is rather outdated and mis-organized, but that's outside the scope of what this change is trying to achieve.	9 years ago
James Bardin	eb02467298	Merge pull request #15588 from hashicorp/jbardin/no-graph-config ... graph should not panic with no config	9 years ago
James Bardin	f10163ecc7	graph should not panic with no config ... The backends replace a nil module tree with an empty one before building the graph, so the graph command needs to do the same.	9 years ago
Martin Atkins	a2ef0ce9a3	Update CHANGELOG.md	9 years ago
Martin Atkins	ac250d2792	plugin/discovery: trim off .exe suffix when parsing filenames ... On Windows systems the plugin binaries use a .exe suffix, which we were misparsing as part of either the "v" or "x" parts of the filename. This fixes #15578.	9 years ago
Dhananjay Balan	fd4a2fa262	website: Correct usage for force-unlock command	9 years ago
Martin Atkins	8e0fefda1f	Merge #15509: End-to-end test harness and some initial tests	9 years ago
Martin Atkins	23f9c8785e	command/e2etest: an initial test for the primary workflow ... This e2etest runs an init, plan, apply, destroy sequence against a test configuration using the real template and null providers downloaded from the official repository. This test _does_ trample a bit on the scope of some already-existing tests, but this is mainly just to check our assumptions about how Terraform behaves to ensure that we can reach our main conclusion here: that the main Terraform workflow commands interact correctly with each other in real use and we can complete the full workflow.	9 years ago
Martin Atkins	52df81ee49	command/e2etest: test that we can install provider plugins ... We already have good tests for the business logic around provider installation, but the existing tests all stub out the main repository server. This test completes that coverage by verifying that the installer is able to run against the real repository and install an official release of the template provider.	9 years ago
Martin Atkins	0e0b0d125a	command/e2etest: "terraform version" test ... This basic test is here primarily because it's one of the few that can run without reaching out to external services, and so it means our usual test runs will catch situations where the main executable build is somehow broken. The version command itself is not very interesting to test, but it's convenient in that its behavior is very predictable and self-contained.	9 years ago
Martin Atkins	fee61a44b4	command/e2etest: end-to-end testing harness ... Previously we had no automated testing of whether we can produce a Terraform executable that actually works. Our various functional tests have good coverage of specific Terraform features and whole operations, but we lacked end-to-end testing of actual usage of the generated binary, without any stubbing. This package is intended as a vehicle for such end-to-end testing. When run normally under "go test" it will produce a build of the main Terraform binary and make it available for tests to execute. The harness exposes a flag for whether tests are allowed to reach out to external network services, controlled with our standard TF_ACC environment variable, so that basic local tests can be safely run as part of "make test" while more elaborate tests can be run easily when desired. It also provides a separate mode of operation where the included script make-archive.sh can be used to produce a self-contained test archive that can be copied to another system to run the tests there. This is intended to allow testing of cross-compiled binaries, by shipping them over to the target OS and architecture to run without requiring a full Go compiler installation on the target system. The goal here is not to test again functionality that's already well-covered by our existing tests, but rather to test chains of normal operations against the build binary that are not otherwise tested together.	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	bb13786663	Merge pull request #15559 from hashicorp/jbardin/protocol-version ... allow missing x-terraform-protocol-version	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
Radek Simko	004f6cc9e2	Update CHANGELOG.md	9 years ago
Radek Simko	f979b8feef	Enforce field names to be alphanum lowercase + underscores (#15562)	9 years ago
James Bardin	2b84e786e9	allow missing x-terraform-protocol-version ... If the release site is missing the "x-terraform-protocol-version" header, we should fetch the latest spec'ed release. Downloading the wrong protocol version can't do any damage, and the version present is more than likely compatible.	9 years ago
James Bardin	87b2c0cf8f	Merge pull request #15556 from hashicorp/jbardin/backend-tests ... backend state tests must honor lineage	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