terraform

Commit Graph

Author	SHA1	Message	Date
Kristin Laemmert	da52170797	configupgrade: fix test (#20863 )	7 years ago
Pam Selle	4c1bb8abd7	Update CHANGELOG.md	7 years ago
Kristin Laemmert	1baa1b907e	configs/configupgrade: detect invalid resource names and print a TODO (#20856 ) * configs/configupgrade: detect invalid resource names and print a TODO message In terraform 0.11 and prior it was possible to start a resource name with a number. This is no longer valid, as the resource name would would be ambiguous with number values in HCL expressions. Fixes #19919 * Update configs/configupgrade/test-fixtures/valid/invalid-resource-name/want/resource.tf Co-Authored-By: mildwonkey <mildwonkey@users.noreply.github.com>	7 years ago
Martin Atkins	003317d7c8	lang: Detect references when a list/set attr is defined using blocks For compatibility with documented patterns from existing providers we are now allowing (via a pre-processing step) any attribute whose type is a list-of-object or set-of-object type to optionally be assigned using one or more blocks whose type is the attribute name. The pre-processing functionality was implemented in previous commits but we were not correctly detecting references within these blocks that are, from the perspective of the primary schema, invalid. Now we'll use an alternative implementation of variable detection that is able to apply the same schema rewriting technique we used to implement the transform and thus can find all of the references as if they were already in their final locations.	7 years ago
Martin Atkins	8746e9e8ad	lang/blocktoattr: ExpandedVariables function Because we handle FixUpBlockAttrs after dynamic block expansion, when resolving variables we unfortunately need to consider the possibility of both dynamic block expansion _and_ the block attrs fixup. To accommodate this we have a variant of dynblock.VariablesHCLDec that instead walks using the configschema.Block representation of the schema and applies the same opportunistic schema rewrite used by FixUpBlockAttrs at each body encountered during the walk.	7 years ago
Martin Atkins	b35bc255d2	vendor: go get github.com/hashicorp/hcl2@master This gives us an extra hook in the dynblock variables analysis that should allow us to also make it subject also to the lang/blocktoattr fixup, to ensure we'll find all the references in spite of these various pre-processing wrappers.	7 years ago
Martin Atkins	87786484ea	lang/eval: Apply attr-as-nested-block fixup in EvalBlock For any block content we evaluate dynamically via this API, we'll make a special allowance for users to optionally write members of a list attribute instead as a sequence of nested blocks, thus allowing some existing provider features that were assuming this capability to continue to support it after v0.12. This should not be used for any new provider features, and should ideally be eventually phased out so that there aren't two similar-but-slightly-different syntaxes for saying the same thing.	7 years ago
Martin Atkins	6dcf8195b8	lang/blocktoattr: Selectively allow block syntax to be used for attributes This preprocessing step allows users to use nested block syntax to specify elements of an attribute that is defined as being a list or set of an object type. This restores part of the unintended flexibility permitted in Terraform v0.11 so that we can work around a few tricky edges where provider implementations were relying on Terraform's failure to validate this in earlier versions. For any body that is pre-processed using this new helper, we will recognize when a configuration author uses nested block syntax with a name that is specified in the schema as an attribute of a suitable type and tweak the schema just in time before decoding to expect that usage and then fix up the result on the way out to conform to the original schema. Achieving this requires an abstraction inversion because only Terraform's high-level schema has enough information to decide how to rewrite the incoming low-level schema. We must therefore here implement HCL's lowest-level API interface in terms of the higher-level abstractions of hcldec and Terraform's configschema. Because of the abstraction inversion this fixup mechanism cannot be used generally for arbitrary HCL bodies but we can use it carefully inside the lang package where its own API can guarantee the necessary invariants for this to work.	7 years ago
Pam Selle	d1c1bc6cdb	Merge pull request #20853 from pselle/err-handling-registry-unresponsive Add friendly error for when registry unresponsive	7 years ago
Kristin Laemmert	931851ca82	update terraform-config-inspect (#20852 )	7 years ago
Sander van Harmelen	86164c0bb4	Merge pull request #20843 from hashicorp/svh/f-force-push backend/local: preserve serial and lineage on failure	7 years ago
Pam Selle	ff7245f27c	Add status link to make message more helpful	7 years ago
Chris Griggs	c69cc88c8b	Merge pull request #20848 from cgriggs01/cgriggs01-jdcloud [Website] Add JDcloud provider	7 years ago
cgriggs01	fc47a78e60	add jdcloud provider links	7 years ago
Pam Selle	d72456d188	Add friendly error for when registry unresponsive If the registry is unresponsive, you will now get an error specific to this, rather than a misleading "provider unavailable" type error. Also adds debug logging for when errors like this may occur	7 years ago
Sander van Harmelen	21cca34716	Fixup the docs for WriteStateForMigration	7 years ago
Sander van Harmelen	57f6e01830	backend/local: preserve serial and lineage on failure When failing to write the state, the local backend writes the state to a local file called `errrored.tfstate`. Previously it would do so by creating a new state file which would use a new serial and lineage. By exorting the existing state file and directly assigning the new state, the serial and lineage are preserved.	7 years ago
Martin Atkins	f302747077	website: Additional explanation for cidrsubnet function Some users are not accustomed to thinking of IP addresses in a bitwise fashion, so the hope here is to give enough of an introduction to that way of thinking for the reader to understand what the "newbits" and "netnum" arguments represent.	7 years ago
James Bardin	a63c1af8e0	Merge pull request #20826 from hashicorp/jbardin/validate-connection merge connection blocks for validation	7 years ago
James Bardin	3c8b46fffe	merge connection blocks for validation The resource connection block was not being validated. Merge the two bodies, with the provider as the override, before validation.	7 years ago
Kristin Laemmert	d5bb09b13b	command/show: refresh is required to show remote state (#20818 )	7 years ago
Alex McLarty	4b9a764eb1	website: Fix typo in null_resource.html.markdown (#20817 ) Fix typo in null_resource.html.markdown	7 years ago
Nick Fagerlund	d0b7771634	website: Simplify wording for split built-in function (#20803 ) The definition of split was referring the built-in function join. However, join is just one of the ways a string might have been created, and this could cause confusion.	7 years ago
Nick Fagerlund	b32cce9637	website: Fix contradictory description of remote state `outputs` object	7 years ago
Nick Fagerlund	499ccd42bf	website: fix broken markdown in modules/composition	7 years ago
Martin Atkins	1f241f8f83	docs: Some updates to the architecture summary This doc was originally written in the middle of Terraform v0.12 development while some refactoring was already in progress. Here we update those parts to refer to where the relevant functionality finally landed, and also update some things that we did not anticipate changing at the time but ended up having to be changed during the v0.12 development anyway.	7 years ago
Martin Atkins	18c88f5a41	docs: Import some existing docs to bootstrap the codebase docs section For a while now we've been gathering some codebase-level docs that felt out-of-place on the main Terraform website (since they are about the implementation, not usage) but we had no existing suitable place to put them. In order to make this information more available (and, hopefully, more likely to stay up-to-date as we change things), here we'll establish the "docs" directory as a place to keep documentation aimed at those who are working on code changes to the Terraform Core codebase. User-oriented docs should never appear in this directory. The Terraform website is always the better place for those. The set of docs here is rudimentary to start and we'll see if it makes sense to expand and reorganize it over time based on the experience with having these initial docs available.	7 years ago
James Bardin	657dddceab	Merge pull request #20799 from hashicorp/jbardin/tests-force-new add (forces new resource) to provider test diffs	7 years ago
Nick Fagerlund	4200b0b2c5	website: Use bullet lists in smaller provider lists, too These are small enough that using multi-columns would just get in the way, but might as well style them similarly.	7 years ago
Nick Fagerlund	b14b967fb7	website: Fix some alphabetization in provider lists	7 years ago
Nick Fagerlund	33118b9b0c	website: List providers vertically instead of horizontally This should make it easier to find items alphabetically, and it DEFINITELY makes it easier to update.	7 years ago
Vangelis Katsikaros	94463894ec	website: "map" a real resource to configuration, not "attach" (#17912 ) In the terraform state documentation the verb "map" is widely used to describe the relationship between an item in the state and in the real world whereas the verb "attach" is not used anywhere.	7 years ago
Nick Fagerlund	428a2c05e7	website: Expand output values docs (#20790 ) For 0.11 I just specified the naming rules; for 0.12, I added some info about referencing values and tightened up the layout of the optional arguments. This commit also syncs up descriptions of `depends_on`.	7 years ago
Nick Fagerlund	53cff99f84	website: Add `workspace show` command to sidebar nav (#20800 )	7 years ago
Guillaume Dupin	4b8d11e2de	Create commands/workspace/show.html.md (#18355 ) Add documentation for `terraform workspace show` command	7 years ago
James Bardin	bb62aba651	add (forces new resource) to provider test diffs Add the (forces new resource) annotation to the diff output for provider tests failures when we can. This helps providers narrow down what might be triggering changes when encountering test failures with the new SDK.	7 years ago
Nick Fagerlund	c06674bac7	website: Clarify that example S3 policy is for an IAM entity (#20791 )	7 years ago
James Bardin	2e15f6f585	Merge pull request #20797 from hashicorp/jbardin/update-goplugin udpate go-plugin	7 years ago
James Bardin	11dba9f86a	udpate go-plugin	7 years ago
Nick Fagerlund	cb4f3004da	website: Fix several spelling errors	7 years ago
Nick Fagerlund	740aff3899	website: Update options for graph command 'legacy' doesn't seem to be a thing anymore, and we were missing some of the other values for -type. Also -no-color doesn't seem to be relevant to this command.	7 years ago
Nick Fagerlund	b61e50be13	website: Use a normal file-based template in example, and expand the explanation of $${thing}	7 years ago
Lars Francke	db6ec472ef	website: Fix documentation glitch and add note about double "$" 1. The double "$" in the template confuses readers 2. As far as I can tell the variable "count" is not used either in this example (it is in the next example though)	7 years ago
Martin Atkins	2a64a00983	core: Upgrade flatmap to JSON when dynamic attributes are present When a resource type schema includes dynamically-typed attributes we can't do any automatic conversion from flatmap to JSON because we don't know how to interpret the keys that start with the dynamically-typed attribute's prefix. To work around that, we'll instead just ask the SDK to do a no-op upgrade (current and target versions are the same) which will convert from flatmap to JSON using the SDK's own logic as a side-effect. This situation should rarely arise in real-world use, but it ends up being very important for the helper/resource provider test harness because it is forced to lower the state back to flatmap repeatedly after every step in order to run legacy checking and processing code.	7 years ago
Martin Atkins	135121562e	helper/plugin: Implement Schema.SkipCoreTypeCheck The previous commit added this flag but did not implement it. Here we implement it by adjusting the shape of schema we return to Terraform Core to mark the attribute as untyped and then ensure that gets handled correctly on the SDK side.	7 years ago
Martin Atkins	7f860dc83e	helper/schema: Schema.SkipCoreTypeCheck flag When running in v0.12-and-higher mode, this will cause the SDK to report the type of the attribute as "any", effectively skipping type checking on the Core side altogether and checking only in the SDK and provider code. The practical impact of this is to restore the v0.11-style checking behavior of allowing object values to be missing certain attributes as long as they are marked as optional in the schema. The SDK can do this because it uses a unified schema model for both object values and nested blocks, while Terraform Core only supports the idea of "optional" when talking about attributes in nested blocks. This is a continuation of the pile of workarounds that also includes the ConfigMode and AsSingle fields, allowing providers to selectively opt out of new v0.12 behaviors in situations where they conflict with decisions made in the design of the providers in our old world where Terraform Core delegated _all_ validation to providers. This is designed as an opt-in so that we can limit its impact only to specific cases where it's needed and minimize the risk of regressions elsewhere. Providers should use this sparingly only in situations where prevailing usage disagrees with the new expectations of Terraform Core in v0.12. This commit only adds the flag, and does not implement any behavior for it yet. That means this commit can exist in both the v0.11 and v0.12 codebases, allowing for API compatibility. A subsequent commit for v0.12 (not included in v0.11) will then implement this behavior.	7 years ago
Justin Downing	1e32ae243c	grammatical updates to comments and docs (#20195 )	7 years ago
Sander van Zoest	42305e62ea	website: Fix a typo in null_resource provisioner page description (#19928 )	7 years ago
Kim Ngo	479964ad66	Merge pull request #20781 from findkim/registry-checksum plugin/discovery: verify registry checksum	7 years ago
Justin Clark	7af7fb3f71	website: access_token is not required in `atlas` backend (#20222 )	7 years ago

1 2 3 4 5 ...

23832 Commits (da521707970109f4866b2c064afdc716632dd016) All Branches Search

23832 Commits (da521707970109f4866b2c064afdc716632dd016)

All Branches