20298 Commits (de50eeb6b69964cda7fbd4d17af83003d3a29dc9)

 

All Branches   

Search

Author	SHA1	Message	Date
Mitchell Hashimoto	de50eeb6b6	website: more registry docs	9 years ago
Mitchell Hashimoto	b4f2fae0a6	website: api docs for the registry	9 years ago
Mitchell Hashimoto	331b6f339a	website: finding and using registry modules	9 years ago
Mitchell Hashimoto	0718e9ce3f	website: standard module structure	9 years ago
Mitchell Hashimoto	bf7f4d243d	website: working on registry docs	9 years ago
Mitchell Hashimoto	1c098ce4ec	website: trivial change to make branch	9 years ago
Chris Marchesi	9504d17bd9	Merge pull request #16036 from hashicorp/f-import-state-testing-id-func ... helper/resource: Add ImportStateIdFunc	9 years ago
Shih Oon Liong	bcfb63098a	website: Example of using maps with local values	9 years ago
Justin Campbell	1f63a96b10	Merge pull request #16041 from justincampbell/website-local-values-usage-example ... docs: Add local values usage example	9 years ago
Justin Campbell	fd4cc78839	docs: Add local values usage example	9 years ago
Radek Simko	9f570a0c84	Merge pull request #16037 from hashicorp/b-readme-logo-url ... docs: Fix logo URL in Readme	9 years ago
Radek Simko	f729ef42ff	docs: Fix logo URL in Readme	9 years ago
Chris Marchesi	dc1f155728	helper/resource: Failure case for ImportStateIdFunc ... Just to make sure returning an error was working.	9 years ago
Chris Marchesi	7bba1d0c95	helper/resource: Add ImportStateIdFunc ... Add an ImportStateIdFunc field to the ImportState testing functionality. This will allow for more powerful generation of complex import state IDs that can't be accomplished by ImportStateId or ImportStateIdPrefix themselves.	9 years ago
James Bardin	25f6e61047	release: clean up after v0.10.4	9 years ago
James Bardin	10df48ef40	v0.10.4	9 years ago
Martin Atkins	7360cf4349	Update CHANGELOG.md	9 years ago
tombuildsstuff	d074b0da29	Obtaining the current metadata before setting it	9 years ago
tombuildsstuff	a10d23dd95	Removing dead code	9 years ago
tombuildsstuff	1425205348	Upgrading to the latest Azure SDK's	9 years ago
James Bardin	f5a3dc09a7	update CHANGELOG.md	9 years ago
Chris Doherty	ec4cecc67b	Merge pull request #15999 from hashicorp/cdoherty/doc-tweak ... Cosmetic doc changes	9 years ago
Jake Champlin	f49d882f06	Merge pull request #16027 from alexwlchan/quotes-in-docs ... Add some missing quotes in the Module docs	9 years ago
Alex Chan	a496b45c2c	Add some missing quotes in the Module docs	9 years ago
Chris Doherty	793b986860	Cosmetic doc changes: ... - Having a map 'foo' with a key 'foo' is confusing. - it's -> its	9 years ago
James Bardin	19f9d1c93a	Merge pull request #16023 from hashicorp/jbardin/update-go-getter ... update go-getter	9 years ago
James Bardin	42764cbe94	update go-getter ... Update to the latest go-getter to support unpacking github release tarballs as modules.	9 years ago
Jake Champlin	a9ef28ff93	Merge pull request #15984 from hashicorp/f-update-policy-vendor ... Deps: Update Depedency for license	9 years ago
James Bardin	2863a51095	Merge pull request #15973 from synthdnb/consul-crash-fix ... Fix crash when using consul backend	9 years ago
Jake Champlin	5d4931cb2e	Update AWS SDK to match AWS provider dep	9 years ago
Tom Harvey	cbb512d374	Updating the AzureRM Backend Documentation (#15990) ... * Updating to reference this has been renamed * Clarifying Blob Storage	9 years ago
Minkyu Kim	f12a237747	Fix crash when using consul backend	9 years ago
Martin Atkins	72da85e927	Update CHANGELOG.md	9 years ago
Martin Atkins	83414beb8f	command: various adjustments to the diff presentation ... The previous diff presentation was rather "wordy", and not very friendly to those who can't see color either because they have color-blindness or because they don't have a color-supporting terminal. This new presentation uses the actual symbols used in the plan output and tries to be more concise. It also uses some framing characters to try to separate the different stages of "terraform plan" to make it easier to visually navigate. The apply command also adopts this new plan presentation, in preparation for "terraform apply" (with interactive plan confirmation) becoming the primary, safe workflow in the next major release. Finally, we standardize on the terminology "perform" and "actions" rather than "execute" and "changes" to reflect the fact that reading is now an action and that isn't actually a _change_.	9 years ago
Martin Atkins	892f60efe0	core: test that we skip hooks for data source destroy ... Data source destroy is an implementation detail and not something that external callers should see or expect.	9 years ago
Martin Atkins	e7a0aa96c8	core: add testHook for testing correct interaction with hooks	9 years ago
Martin Atkins	6712192724	core: don't advertise data source destroy via hooks ... The fact that we clean up data source state by applying a "destroy" action for them is an implementation detail, and so should not be visible to outside callers or to the user. Signalling these as real destroys creates confusion for users because they see Terraform say things like: data.template_file.foo: Refreshing state..." ...which, to an understandably-nervous sysadmin, might make them suspect that the underlying object was deleted, rather than just Terraform's record of it.	9 years ago
Martin Atkins	d4efc95191	command: show resource actions using resource addresses ... Previously we were using the internal resource id syntax in the UI. Now we'll use the standard user-facing resource address syntax instead.	9 years ago
Martin Atkins	3ea159297c	command/format: improve consistency of plan results ... Previously the rendered plan output was constructed directly from the core plan and then annotated with counts derived from the count hook. At various places we applied little adjustments to deal with the fact that the user-facing diff model is not identical to the internal diff model, including the special handling of data source reads and destroys. Since this logic was just muddled into the rendering code, it behaved inconsistently with the tally of adds, updates and deletes. This change reworks the plan formatter so that it happens in two stages: - First, we produce a specialized Plan object that is tailored for use in the UI. This applies all the relevant logic to transform the physical model into the user model. - Second, we do a straightforward visual rendering of the display-oriented plan object. For the moment this is slightly overkill since there's only one rendering path, but it does give us the benefit of letting the counts be derived from the same data as the full detailed diff, ensuring that they'll stay consistent. Later we may choose to have other UIs for plans, such as a machine-readable output intended to drive a web UI. In that case, we'd want the web UI to consume a serialization of the _display-oriented_ plan so that it doesn't need to re-implement all of these UI special cases. This introduces to core a new diff action type for "refresh". Currently this is used _only_ in the UI layer, to represent data source reads. Later it would be good to use this type for the core diff as well, to improve consistency, but that is left for another day to keep this change focused on the UI.	9 years ago
Martin Atkins	4750f0607d	core: stabilize ResourceAddress.Less results ... The implementation of ResourceAddress.Less was flawed because it was only testing each field in the "less than" direction, and falling through in cases where an earlier field compared greater than a later one. Now we test for inequality first as the selector, and only fall through if the two values for a given field are equal.	9 years ago
Martin Atkins	4739cb6597	Update CHANGELOG.md	9 years ago
Martin Atkins	0a342e8dc2	config: allow local value interpolations in count ... There is some additional, early validation on the "count" meta-argument that verifies that only suitable variable types are used, and adding local values to this whitelist was missed in the initial implementation.	9 years ago
Martin Atkins	8cd0ee80e5	config: merge/append for local values ... It seems that this somehow got lost in the commit/rebase shuffle and wasn't caught by the tests that _did_ make it because they were all using just one file. As a result of this bug, locals would fail to work correctly in any configuration with more than one .tf file. Along with restoring the append/merge behavior, this also reworks some of the tests to exercise the multi-file case as better insurance against regressions of this sort in future. This fixes #15969.	9 years ago
James Bardin	6bd9e3f2ab	Merge pull request #15976 from hashicorp/jbardin/GH-15972 ... Fix crash in consul backend	9 years ago
James Bardin	76eb65c911	Fix crash in consul backend ... A TLS config was being assigned to a Transport in a nil http.Client. The Transport is built in the consul config by default, but the http.Client is not built until later in NewClient.	9 years ago
Martin Atkins	adb6a089ff	release: clean up after v0.10.3	9 years ago
Martin Atkins	1511d447e7	v0.10.3	9 years ago
Martin Atkins	6a4498ba76	provisioner/salt-masterless: add "_file" suffix to "minion_config" ... In #15870 we got good feedback that it'd be more useful to have the various filename-accepting arguments on this provisioner instead accept strings that represent the contents of such files, so that they can be generated from elsewhere in the Terraform config. This change does not achieve that, but it does make room for doing this later by renaming "minion_config" to "minion_config_file" so that we can later add a "minion_config" option alongside that takes the file content, and deprecate "minion_config_file". Ideally we'd just implement the requested change immediately, but unfortunately the release schedule doesn't have time for this so this is a pragmatic change to allow us to make the full requested change at a later date without backward incompatibilities. This change is safe because the salt-masterless provisioner has not yet been included in a release at the time of this commit.	9 years ago
Martin Atkins	4aa67f0bfc	provisioner/salt-masterless: fix crash processing connection config ... The code here was previously assuming that d.State() was equivalent to the schema.ProvRawStateKey due to them both being of type InstanceState, but that is in fact not true since a state object contains some transient information that is _not_ part of the persisted state, including the connection information we need here. Calling ResourceData.State() constructs a _new_ state based on its stored values, so the constructed object is lacking this transient information. We need to use the specific state object provided by the caller in order to get access to the transient connection configuration. Unfortunately there is no automated test coverage for this because we have no good story for testing provisioners that use "communicator". While such tests could potentially be written, we'd like to get this in somewhat quickly to unblock a release, rather than delaying to design and implement some sort of mocking system for this.	9 years ago
James Bardin	593bf683dc	Merge pull request #15448 from hashicorp/jbardin/state-meta-equal ... make sure marshaled Meta fields are still equal	9 years ago