terraform

Commit Graph

Author	SHA1	Message	Date
Paul Thrasher	151c91ffda	use scanner for reading logs Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>	7 years ago
Paul Thrasher	0e27a8862f	remove duplicate remote output line Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>	7 years ago
Sander van Harmelen	bb12206bca	Fixup the tests	7 years ago
Sander van Harmelen	7cf744241a	Do not use a scanner to read the logs Using a scanner can cause issues when reading long lines. Also make sure we return the error correctly while planning.	7 years ago
Sander van Harmelen	cc38debace	Fixup the `go-tfe` update ``` go get github.com/hashicorp/go-tfe go mod tidy go mod vendor ```	7 years ago
Paul Thrasher	c7a023a95c	update test for new go-tfe version Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>	7 years ago
Paul Thrasher	aece05320b	update go-tfe to v0.3.16 Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>	7 years ago
Paul Thrasher	53f977bee2	TFCE api correct pluralization Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>	7 years ago
Paul Thrasher	e479bd5dc3	update to latest go-tfe same version number but pointing to a new sha Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>	7 years ago
Chris Griggs	b7705d20a0	Merge pull request #21098 from hashicorp/cgriggs01-add-gridscale [Website] Add Gridscale provider	7 years ago
Chris Griggs	103f56e0a3	Merge pull request #21090 from hashicorp/cgriggs01-name-update [Website] Fix FortiOS typo	7 years ago
cgriggs01	bad3c57f00	[Website] Add Gridscale provider	7 years ago
Martin Atkins	4897c0554d	vendor: go get github.com/hashicorp/go-msgpack@v0.5.4 By upgrading this to a version that supports Go Modules, we can avoid the redundant dependencies labix.org/v2/mgo and launchpad.net/gocheck. These dependencies come via hashicorp/consul, which we have vendored for the Consul backend. There are no changes to the go-msgpack code here; we're just adopting a newer version that has a go.mod present so that its dependencies can be determined more accurately.	7 years ago
Radek Simko	e8ee3f14a4	Merge pull request #21094 from hashicorp/fix-plugin-discovery-quoting plugin/discovery: Fix quoting of provider name	7 years ago
Radek Simko	b171997b39	plugin/discovery: Fix quoting of provider name	7 years ago
Kristin Laemmert	2573d549c2	Update CHANGELOG.md	7 years ago
Kit Ewbank	efc08de5d6	lang/funcs: add 'strrev' interpolation function. (#21091 )	7 years ago
cgriggs01	bd1b2c8641	fix FortiOS caps	7 years ago
Kristin Laemmert	9327eedb04	internal/initwd: follow local module path symlink (#21063 ) * internal/initwd: follow local module path symlink Fixes #21060 While a previous commit fixed a problem when the local module directory contained a symlink, it did not account for the possibility that the entire directory was a symlink.	7 years ago
James Bardin	64f419ac76	Merge pull request #21077 from hashicorp/jbardin/map-shims Fixes for maps in shims	7 years ago
James Bardin	2fe0f9376a	change "preferDst" to "apply" in normalizeNullVals Inverting this and renaming it makes it align with the current use of that boolean argument.	7 years ago
James Bardin	0696cf7245	don't retain removed map values Make sure values removed from a map during apply are not copied into the new map. The broken test is no longer valid in this case, and the updated diff.Apply should prevent the case it used to cover.	7 years ago
James Bardin	0f883b118a	test that computed maps are applied correctly Verify that a computed map which is not correctly marked as unknown in the plan is still applied correctly.	7 years ago
James Bardin	3d46c04e28	Merge pull request #21068 from hashicorp/jbardin/get-ok-exists delete unknown values from apply config altogether	7 years ago
James Bardin	67395306e1	delete unknown values from apply config altogether removeConfigUnknowns need to remove the value completely from the config map. Removing this value allows GetOk and GetOkExists to indicate if the value was set in the config in the case of an Optional+Computed attribute.	7 years ago
Ross McKelvie	ce1fba5817	website: update required_providers block for terraform 0.12 compatibility	7 years ago
Ryan	1a53575b15	build: use correct link for GCP provider in GitHub issue template	7 years ago
Martin Atkins	168592825e	release: clean up after v0.12.0-beta2	7 years ago
Chris Griggs	aeabdf1a0d	Merge pull request #21054 from cgriggs01/cgriggs01-community-patch [Website] Adding community provider	7 years ago
Pam Selle	3f68b12e3a	Merge pull request #20959 from mars/patch-1 Update CHANGELOG for #20561	7 years ago
Mars Hall	67b9a11fad	Update CHANGELOG for #20561	7 years ago
Martin Atkins	533cbf4c3f	website: Update "Local Values" docs to use v0.12 syntax in example There was some leftover v0.11-style interpolation syntax here. We prefer to use a "naked" expression in situations like this where the result isn't a string, because interpolations returning non-strings is a common source of confusion for new users.	7 years ago
Chris Griggs	f66b563ccd	Merge pull request #21051 from cgriggs01/cgriggs01-fortios-links [Website] Adding Fortios provider links	7 years ago
cgriggs01	55b816853a	[Website] Adding Fortios provider links	7 years ago
Martin Atkins	62d32e9bb3	website: Fix incorrect example in Module Composition page The example above treats recordsets as a list, but the declaration was for a single object.	7 years ago
cgriggs01	26d515e40a	Adding community provider	7 years ago
Alex Somesan	275e0a53f2	Merge pull request #20851 from hashicorp/doc-validatefunc-maps Document that ValidateFunc works on maps.	7 years ago
Paul Tyng	6bd7fdbb6b	Merge pull request #21043 from hashicorp/paultyng-patch-1 godoc typo	7 years ago
Martin Atkins	2238fbda1b	website: v0.12 upgrade guide about list variables and brackets	7 years ago
Alex Somesan	01a169c66f	make fmt	7 years ago
Kristin Laemmert	83dea200c0	Update CHANGELOG.md	7 years ago
Przemysław Dąbek	9605b093d9	command/graph: use user-supplied plugin path when running graph command (#18083 )	7 years ago
Paul Tyng	ab2d09b0cb	godoc typo	7 years ago
Martin Atkins	cbc8d1eba2	core: Input variables are always unknown during validate Earlier on in the v0.12 development cycle we made the decision that the validation walk should consider input values to always be unknown so that validation is checking validity for all possible inputs rather than for a specific set of inputs; checking for a specific set of inputs is the responsibility of the plan walk. However, we didn't implement that in the best way: we made the "terraform validate" command force all of the input variables to unknown but that was insufficient because it didn't also affect the implicit validation walk we do as part of "terraform plan" and "terraform apply", causing those to produce confusingly-different results. Instead, we'll address the problem directly in the reference resolver code, ensuring that all variable values will always be treated as an unknown (of the declared type, so type checking is still possible) during any validate walk, regardless of which command is running it.	7 years ago
Martin Atkins	d7f23f0beb	configs/configupgrade: Don't panic if analyzer fails Previously we were trying to access a field of the analysis object before checking if analysis produced errors. The analysis function usually returns a nil analysis on error, so this would result in a panic whenever that happened. Now we'll dereference the analysis object pointer only after checking for errors, so we'll get a chance to report the analysis error to the user.	7 years ago
Alex Somesan	0395c3ac58	Re-phrase docs to enumerate types which support ValidateFunc	7 years ago
Martin Atkins	1bb47ab9a5	configs/configupgrade: Preserve comments on items in object exprs The expression upgrade functionality mostly ignores comments because in the old language the syntax prevented comments from appearing in the middle of expressions, but there was one exception: object expressions. Because HCL 1 used ObjectType both for blocks and for object expressions, that is the one situation where something we consider to be an expression could have inline attached comments in the old language. We migrate these here so we don't lose these comments that don't appear anywhere else. Other comments get gathered up into a general comments set maintained inside the analysis object and so will be printed out as required _between_ expressions, just as they did before.	7 years ago
Martin Atkins	861a2ebf26	helper/schema: Use a more targeted shim for nested set diff applying We previously attempted to make the special diff apply behavior for nested sets of objects work with attribute mode by totally discarding attribute mode for all shims. In practice, that is too broad a solution: there are lots of other shimming behaviors that we _don't_ want when attribute mode is enabled. In particular, we need to make sure that the difference between null and empty can be seen in configuration. As a compromise then, we will give all of the shims access to the real ConfigMode and then do a more specialized fixup within the diff-apply logic: we'll construct a synthetic nested block schema and then use that to run our existing logic to deal with nested sets of objects, while using the previous behavior in all other cases. In effect, this means that the special new behavior only applies when the provider uses the opt-in ConfigMode setting on a particular attribute, and thus this change has much less risk of causing broad, unintended regressions elsewhere.	7 years ago
Martin Atkins	5f29339121	Update CHANGELOG.md	7 years ago
Martin Atkins	ff2de9c818	core: Keep old value on error even for delete When an operation fails, providers may return a null new value rather than returning a partial state. In that case, we'd prefer to keep the old value so that we stand the best chance of being able to retry on a subsequent run. Previously we were making an exception for the delete action, allowing the result of that to be null even when an error is returned. In practice that was a bad idea because it would cause Terraform to lose track of the object even though it might not actually have been deleted. Now we'll retain the old object even in the delete case. Providers can still return partial new objects if they were able to partially complete a delete operation, in which case we'll discard what we had before, but if the result is null with errors then we'll assume the delete failed entirely and so just keep the old state as-is, giving us the opportunity to refresh it on the next run to see if anything actually happened after all. (This also includes a new resource in the test provider which isn't used by the patch but was useful for some manual UX testing here, so I thought I'd include it in case it's similarly useful in future, given how simple its implementation is.)	7 years ago

1 2 3 4 5 ...

23961 Commits (151c91ffdae99e14d45883df5e4ce2f84cfc6e17) All Branches Search

23961 Commits (151c91ffdae99e14d45883df5e4ce2f84cfc6e17)

All Branches