terraform

Commit Graph

Author	SHA1	Message	Date
Nick Fagerlund	0834813ed5	website: Write new content for CLI docs front page	7 years ago
Nick Fagerlund	13166df619	website: move docs/index.html to docs/cli-index.html Terraform is way bigger than the core CLI tools and the language now, and the docs have grown accordingly. So we're adding a global index page to help users get around the many sections of the docs site, and bumping the CLI/core docs down so they're no longer at the top of the hierarchy. The "right" (as in, conceptually pure) way to do this would be to actually create a new level of directory hierarchy in between. But that would be real expensive and annoying — the amount of 301s and links to edit would be monumental, and it wouldn't gain us much beyond a certain picture-straightening satisfaction, so I'm resisting the temptation.	7 years ago
Martin Atkins	1987a92386	helper/schema: Implementation of the AsSingle mechanism The previous commit added a new flag to schema.Schema which is documented to make a list with MaxItems: 1 be presented to Terraform Core as a single value instead, giving a way to switch to non-list nested resources without it being a breaking change for Terraform v0.11 users as long as it's done prior to a provider's first v0.12-compatible release. This is the implementation of that mechanism. It's intentionally implemented as a suite of extra fixups rather than direct modifications to existing shim code because we want to ensure that this has no effect whatsoever on the result of a resource type that _isn't_ using AsSingle. Although there is some small unit test coverage of the fixup steps here, the primary testing for this is in the test provider since the integration of all of these fixup steps in the correct order is the more important result than any of the intermediate fixup steps.	7 years ago
Martin Atkins	1c8150428f	helper/schema: Schema.AsSingle flag This setting indicates that an attribute defined as TypeList or TypeSet should be presented to Terraform Core as a single value instead when running in Terraform v0.12 or later. It has no effect for Terraform v0.10 or v0.11. This commit just introduces the setting without any associated behavior, so it can be included in both the v0.12 and v0.11 branches. A subsequent commit only to the v0.12 branch will introduce the behavior as part of the protocol version 5 shims.	7 years ago
Kristin Laemmert	9d0d564ec7	`terraform show` and `terraform providers schema -json` should return valid json (#20697 ) * command/providers schemas: return empty json object if config parses successfully but no providers found * command/show (state): return an empty object if state is nil	7 years ago
James Bardin	035e89696c	Merge pull request #20698 from hashicorp/jbardin/null-string don't try to treat "null" as json in diff output	7 years ago
James Bardin	0569e39788	don't try to treat "null" as json in diff output Trying to decode and write "null" as json will panic, since it decodes to nil.	7 years ago
Kristin Laemmert	2c60140cad	configs: do not panic if module version is a variable (#20681 ) Fixes #20653	7 years ago
Brian Flad	87f1877a81	Merge pull request #20675 from hashicorp/f-file-function-recommendation config: Mention other file hashing functions when file() detects unsupported contents	7 years ago
Nick Fagerlund	6c346b5740	website: Tweak 0.12 module content for 0.11 ...well, I was ALMOST right in the previous commit.	7 years ago
Nick Fagerlund	34e90ff3c1	website: Fix broken links to modules/usage and modules/create As part of this, I'm copying the entire text of the 0.12 docs/configuration/modules.html page into docs/configuration-0-11/modules.html — some of the 0.11 pages needed to be able to link to the moved content, I didn't want to jump versions jarringly, and a close reading didn't reveal anything in there that's inaccurate for 0.11.	7 years ago
Nick Fagerlund	50f76dd566	website: fix broken anchor link (to #for-expressions)	7 years ago
Nick Fagerlund	3977598edb	website: remote backend also supports multiple workspaces	7 years ago
Nick Fagerlund	71af3bc3ec	website: Fix nav link activation for json syntax page	7 years ago
Nick Fagerlund	094a5d65d3	website: Use a middleman partial for "other docs" list instead of hardcoding it This relies on a commit in the terraform-website repo, and should make updating that list much less annoying.	7 years ago
James Bardin	4abdad7ab9	Merge pull request #20680 from hashicorp/jbardin/read-normalization ReadResource normalization	7 years ago
James Bardin	4006c0fc84	add test for set value drift The changed value for the set attribute should be correctly read from the provider.	7 years ago
James Bardin	e080706e2e	treat normalization during ReadResource like Plan This will allow resources to return an unexpected change to set blocks and attributes, otherwise we could mask these changes during normalization. Change the "plan" argument in normalizeNullValues to "preferDst" to more accurately describe what the option is doing, since it no longer applies only to PlanResourceChange.	7 years ago
Chris Griggs	2d2ad0d5ca	Merge pull request #20677 from cgriggs01/cgriggs01-community-providers [Website] New Community Providers	7 years ago
cgriggs01	489d72e77f	New community providers	7 years ago
Kristin Laemmert	a15a4acf2f	configs/configupgrade: detect possible relative module sources (#20646 ) * configs/configupgrade: detect possible relative module sources If a module source appears to be a relative local path but does not have a preceding ./, print a #TODO message for the user. * internal/initwd: limit go-getter detectors to those supported by terraform * internal/initwd: move isMaybeRelativeLocalPath check into getWithGoGetter To avoid making two calls to getter.Detect, which potentially makes non-trivial API calls, the "isMaybeRelativeLocalPath" check was moved to a later step and a custom error type was added so user-friendly diagnostics could be displayed in the event that a possible relative local path was detected.	7 years ago
Radek Simko	29f2776cc7	Merge pull request #20614 from hashicorp/docs-remote-state-012 docs: Differentiate 0.11/0.12 in terraform_remote_state	7 years ago
Brian Flad	398fe8652d	config: Mention other file hashing functions when file() detects unsupported contents Reference: https://github.com/hashicorp/terraform/issues/20664	7 years ago
Radek Simko	142ecfefe0	docs: Differentiate 0.11/0.12 in terraform_remote_state	7 years ago
Gyorgy Hrabovszki	2b726a892f	website: Fix typo in the Local Values documentation	7 years ago
James Bardin	ccd62283fb	Merge pull request #20657 from hashicorp/jbardin/diff-apply-shim sdk shim normalization	7 years ago
James Bardin	17425c60f3	Merge pull request #20662 from hashicorp/jbardin/unlock check for errors when loading a backend config	7 years ago
James Bardin	a8df5586c0	check for errors when loading a backend config We can't dereference the config module if there were any errors loading it.	7 years ago
James Bardin	6ecf9b143b	we can normalize nulls in Read again This should be the final change from removing the flatmap normalization. Since we're no longer trying to a consistent zero or null value in the flatmap config, rather we're trying to maintain the previously applied value, ReadResource also needs to apply the normalizeNullValues step in order to prevent unexpected diffs.	7 years ago
Radek Simko	8c966a85ee	Merge pull request #20648 from hashicorp/vendor-bump-x-net vendor: golang.org/x/net@d8887717615a	7 years ago
Brian Flad	ffebe54779	Update CHANGELOG for #20654	7 years ago
Ivan Pedersen	1f990dcd9f	README: Fix typo	7 years ago
Brian Flad	7a135c98d8	Merge pull request #20654 from hashicorp/b-filebase64sha256-sha512 lang/funcs: Fix filebase64sha256 function hashing algorithm	7 years ago
Brian Flad	81bdaa8c38	lang/funcs: Fix filebase64sha256 function hashing algorithm Reference: https://github.com/hashicorp/terraform/issues/20652 The implementation and testing were incorrectly referencing SHA-512 instead of SHA-256.	7 years ago
James Bardin	11ec3a420e	remove normalizeFlatmapContainers This method was added early on when the diff was being applied as the legacy code would have done, which is no longer the case. Everything that normalizeFlatmapContainers does should be covered by the combination of the initial diff.Apply and the normalizeNullValues on the final cty.Value.	7 years ago
James Bardin	892674a3f9	don't recalculate existing block counts in diff If a block is uneffected by diffs, keep the block count value regardless of what it is. Blocks containing zero values will often be represented by only the count value.	7 years ago
James Bardin	4c23e990e2	add test for complex schema diff apply This schema was taken from an actual google resource which often shows perpetual diffs.	7 years ago
Radek Simko	5205d21f1e	vendor: golang.org/x/net@d8887717615a	7 years ago
Martin Atkins	4de0b33097	helper/schema: Honor ConfigMode when building core schema This makes some slight adjustments to the shape of the schema we present to Terraform Core without affecting how it is consumed by the SDK and thus the provider. This mechanism is designed specifically to avoid changing how the schema is interpreted by the SDK itself or by the provider, so that prior behavior can be preserved in Terraform v0.11 mode. This also includes a new rule that Computed-only (i.e. not also Optional) schemas _always_ map to attributes, because that is a better mapping of the intent: they are object values to be used in expressions. Nested blocks conceptually represent nested objects that are in some sense independent of what they are embedded in, and so they cannot themselves be computed.	7 years ago
Martin Atkins	a6d322edec	helper/schema: ConfigMode field in Schema This allows a provider developer slightly more control over how an SDK schema is mapped into the Terraform configuration language, overriding some default assumptions. ConfigMode overrides the default assumption that a schema with an Elem of type Resource is to be mapped to configuration as a nested block, allowing mapping as an attribute containing an object type instead. These behaviors only apply when a provider is being used with Terraform v0.12 or later. They are ignored altogether in Terraform v0.11 mode, to preserve compatibility. We are adding these primarily to allow the v0.12 version of a resource type schema to be specified to match the prevailing usage of it in existing configurations, in situations where the default mapping to v0.12 concepts is not appropriate. This commit adds only the fields themselves and the InternalValidate rules for them. A subsequent commit for Terraform v0.12 will add the behavior as part of the protocol version 5 shim layer.	7 years ago
Kristin Laemmert	bf04503f04	internal/initwd: identify possible relative module sources Identify module sources that look like relative paths ("child" instead of "./child", for example) and surface a helpful error. Previously, such module sources would be passed to go-getter, which would fail because it was expecting an absolute, or properly relative, path. This commit moves the check for improper relative paths sooner so a user-friendly error can be displayed.	7 years ago
James Bardin	420736333f	Merge pull request #20641 from hashicorp/jbardin/null-computed-blocks stop removing empty flatmap containers	7 years ago
Rupesh Reddy Tumu	fddb52f05c	website: Fix various typos in the config function documentation	7 years ago
James Bardin	9d4bb6ec14	stop removing empty flatmap containers As we've improved the cty.Value normalization, we need to remove normalization procedures from the flatmap handling. Keeping the empty containers in the flatmap will prevent unexpected nils from being added to some schema configurations	7 years ago
Martin Atkins	36bb9b462c	website: "for" expression examples to use canonical formatting The "terraform fmt" command produces a different canonical form than we were showing in our examples here. Our examples should always reflect the conventions applied by "terraform fmt" to avoid confusion. (This particular decision is a pragmatic one because the formatter design needs to use the same rules for the colon in the ? : conditional operator as for the colon in "for" expressions.)	7 years ago
Martin Atkins	0a9959cbe4	website: References to Resource Attributes Since references to attributes of resources are by far the most common reference type, and the mapping of resource type config to the attributes is not always obvious, here we give some real examples of patterns for accessing different configuration constructs within resource blocks along with the resource type's exported attributes. Since we don't have any real examples of labelled nested blocks yet (the current SDK doesn't support them) I've included a hypothetical example for now just to establish the patterns around them in preparation for beginning to introduce them as we roll out this feature in the SDK.	7 years ago
David Chwalisz	ddb7e0ab20	fix `Publishing Modules` link of website documentation. Currently links to [Creating Modules](https://www.terraform.io/docs/modules/create.html) page. Should link to [Publishing Modules](https://www.terraform.io/docs/modules/publish.html) page. fixes #20636	7 years ago
Martin Atkins	2d41c1009b	command/format: Diffs for NestingMap block types Our initial prototype of new-style diff rendering excluded this because the old SDK has no support for this construct. However, we want to be able to introduce this construct in the new SDK without breaking compatibility with existing versions of Terraform Core, so we need to implement it now so it's ready to be used once the SDK implements it. The key associated with each block allows us to properly correlate the items to recognize the difference between an in-place update of an existing block and the addition/deletion of a block.	7 years ago
Martin Atkins	dd1fa322a7	command/format: Support list/map blocks with dynamic-typed attrs Our null-to-empty normalization was previously assuming these would always be collection types, but that isn't true when a block contains something dynamic since we must then use tuple or object types instead to properly represent all of the individual element types.	7 years ago
Martin Atkins	69772b11b1	command/format: test for diff rendering with dynamic-typed subattrs We use cty a little differently when a nested list block contains a dynamically-typed attribute: it appears as a tuple value instead of a list value so that we can retain the individual types of each element. Here we introduce a test for that case, but doing so required also making the runTestCases function handle types in a stricter way so that it will produce planned values that match how Terraform Core would do it, including the necessary late-bound type information for the dynamically-typed attribute.	7 years ago

1 2 3 4 5 ...

23738 Commits (0834813ed5bb976fbe22ab5e08cf8675cce46ba6) All Branches Search

23738 Commits (0834813ed5bb976fbe22ab5e08cf8675cce46ba6)

All Branches