terraform

Commit Graph

Author	SHA1	Message	Date
Martin Atkins	efe78b2910	main: new global option -chdir This new option is intended to address the previous inconsistencies where some older subcommands supported partially changing the target directory (where Terraform would use the new directory inconsistently) where newer commands did not support that override at all. Instead, now Terraform will accept a -chdir command at the start of the command line (before the subcommand) and will interpret it as a request to direct all actions that would normally be taken in the current working directory into the target directory instead. This is similar to options offered by some other similar tools, such as the -C option in "make". The new option is only accepted at the start of the command line (before the subcommand) as a way to reflect that it is a global command (not specific to a particular subcommand) and that it takes effect _before_ executing the subcommand. This also means it'll be forced to appear before any other command-specific arguments that take file paths, which hopefully communicates that those other arguments are interpreted relative to the overridden path. As a measure of pragmatism for existing uses, the path.cwd object in the Terraform language will continue to return the _original_ working directory (ignoring -chdir), in case that is important in some exceptional workflows. The path.root object gives the root module directory, which will always match the overriden working directory unless the user simultaneously uses one of the legacy directory override arguments, which is not a pattern we intend to support in the long run. As a first step down the deprecation path, this commit adjusts the documentation to de-emphasize the inconsistent old command line arguments, including specific guidance on what to use instead for the main three workflow commands, but all of those options remain supported in the same way as they were before. In a later commit we'll make those arguments produce a visible deprecation warning in Terraform's output, and then in an even later commit we'll remove them entirely so that -chdir is the single supported way to run Terraform from a directory other than the one containing the root module configuration.	6 years ago
Kristin Laemmert	883e4487a2	terraform: add GraphNodeExecutable interface (#26132 ) This introduces a new GraphNode, GraphNodeExecutable, which will gradually replace GraphNodeEvalable as part of the overall removal of EvalTree()s. Terraform's Graph.walk function will now check if a node is GraphNodeExecutable and run walker.Execute instead of running through the EvalTree() and Eval(). For the time being, terraform will panic if a node implements both GraphNodeExecutable and GraphNodeEvalable. This will be removed when we've finished removing all GraphNodeEvalable implementations. The new GraphWalker function, Execute(), is meant to replace both EnterEvalTree and ExitEvalTree, and wraps the call to the GraphNodeExecutable's Execute function.	6 years ago
Alisdair McDiarmid	42753e7dcc	Merge pull request #26122 from hashicorp/alisdair/document-jsonencode-html-escape-behaviour Document jsonencode HTML escape behaviour	6 years ago
Alisdair McDiarmid	9f19034fee	website: Document jsonencode entity escaping	6 years ago
Alisdair McDiarmid	c7568ccceb	lang: Add test for jsonencode entity escaping The encoding/json package escapes some HTML-specific characters to prevent JSON from being misinterpreted when in the context of an HTML document. Terraform 0.11 used this behaviour, and to preserve backwards compatibility we are continuing to do so moving forward. This commit adds an explicit test to document that this is intentional, not a bug.	6 years ago
Kristin Laemmert	79e35941f5	Update CHANGELOG.md	6 years ago
Graham Hargreaves	e9394dfb38	command/clistate: Return an error on unlock failure (#25729 ) * Return an error on unlock failure When the lock can't be released return the err even if there is no previous error with the current action. This allows faster failure in CI/CD systems. Without this failure to remove the lock would result in the failure happening on a subsequent plan or apply which slows down the feedback loop in automated systems. * Update command/clistate/state.go Accept review suggestion Co-authored-by: ZymoticB <ZymoticB@users.noreply.github.com> * add test Co-authored-by: ZymoticB <ZymoticB@users.noreply.github.com> Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	6 years ago
Kristin Laemmert	9fba422592	Update CHANGELOG.md FIRST	6 years ago
Kristin Laemmert	e6e35f2077	deps: bump go-cty version (#26079 ) go-cty v1.6.1 fixes a panic in the `element` function when called with a negative offset.	6 years ago
Alisdair McDiarmid	b4017f693d	version: Main branch is now tracking 0.14.0	6 years ago
Martin Atkins	b0da5b1ce5	core: Remove the last few HIL remnants We've not been using HIL in the main codepaths since Terraform 0.12, but some references to it (and some supporting functionality in Terraform) stuck around due to interactions with types we'd kept around to support legacy shims. However, removing the configs.RawConfig field from terraform.ResourceConfig disconnects that subtree of dependencies from everything else, allowing us to remove it. This is safe because the only remaining uses of terraform.ResourceConfig are shims from values that were already evaluated using the HCL 2 API, and thus they never need the "just in time" HIL evaluation that ResourceConfig.interpolateForce used to do. We also had some HIL references in configs/hcl2shim that were previously in support of the "terraform 0.12upgrade" command, but the implementation of that command is now removed. There was one remaining reference to HIL in a now-unused function in the helper/schema package, which I removed entirely here. This then allows us to remove the HIL dependency entirely, and also to clean up some remaining old remants of the legacy "config" package that we'd recently moved into the "configs" package pending further pruning.	6 years ago
Nick Fagerlund	56c0e35243	website: Fix copy-paste error	6 years ago
Nick Fagerlund	a4776bfb40	website: Clarify `locals` vs. `local.thing` distinction The subtle difference in keywords when creating vs. accessing locals trips people up, even more than the "variable" vs. "var" distinction. It deserves its own subheader on the page, plus a nice noisy callout.	6 years ago
Lance Kind	eb7a427fba	Update locals.html.md I've just wasted an hour to two hours trying to find the problem to finally realize that although I declare a "locals" block, it's referred to as "local". This is pretty weird! So let's be be clear about this.	6 years ago
Petros Kolyvas	fa4917172d	Small typo in the internals link to the provider network mirror protocol page (#26098 )	6 years ago
Alisdair McDiarmid	cd1a6f09df	Update CHANGELOG to track work on v0.14.0	6 years ago
hashicorp-ci	42835119d4	Cleanup after v0.13.2 release	6 years ago
hashicorp-ci	01ed00f32a	Release v0.13.2	6 years ago
Kristin Laemmert	503fd1ca06	Update CHANGELOG.md	6 years ago
Matt Kasa	c2e35ae3b5	backend/http: add support for configuration by environment variable (#25439 )	6 years ago
Justin Campbell	24f20177ee	website: Omitunnecessary instruction fror Registry The GitHub Action passes this in already.	6 years ago
Alisdair McDiarmid	19a057226b	Update CHANGELOG.md	6 years ago
Alisdair McDiarmid	45ac265d74	Merge pull request #26066 from hashicorp/alisdair/init-legacy-providers-required-by-state command: Better in-house provider install errors	6 years ago
Alisdair McDiarmid	f795083225	website: Update 0.13 upgrade for legacy providers The error diagnostic shown when legacy state contains resources from in-house providers has changed, so update references to it in the 0.13 upgrade guide.	6 years ago
Alisdair McDiarmid	9f824c53a5	command: Better in-house provider install errors When init attempts to install a legacy provider required by state and fails, but another provider with the same type is successfully installed, this almost definitely means that the user is migrating an in-house provider. The solution here is to use the `terraform state replace-provider` subcommand. This commit makes that next step clearer, by detecting this specific case, and displaying a list of commands to fix the existing state provider references.	6 years ago
Alisdair McDiarmid	3547f9e368	format: Don't wrap space-prefixed diag details Diagnostic detail lines sometimes contain lines which include commands suggested for the user to execute. By convention, these start with leading whitespace to indicate that they are not prose. This commit changes the diagnostic formatter to wrap each line of the detail separately, and skips word wrapping for lines prefixed with space. This prevents ugly and confusing wrapping of long command lines.	6 years ago
Martin Atkins	6b4ed241d3	docs: Provider protocol wire format for values Although we have in this same directory the protocol buffers schemas for the static parts of the provider wire protocol, many of the protocol messages include DynamicValue messages that are presented in a nested dynamic serialization format. That format was previously not documented, and was thus defined only by the implementation. Terraform happens to use a third-party library to implement parts of this encoding, which means that the rules were even harder to track down from reading the code. Regardless of how Terraform happens to implement its serialization and deserialization of DynamicValue, it's the wire format that is contractual and so this document is an implementation-agnostic description of the mapping rules for serializing any Terraform Language value by reference to a provider-defined schema. All future changes to the rules described in here must be backward compatible until protocol major version 6, which is not currently planned.	6 years ago
Paul Tyng	0fae10a886	Add GitHub action instructions to publishing (#26076 ) Co-authored-by: Justin Campbell <justin@justincampbell.me>	6 years ago
Pam Selle	639cd28a67	Merge pull request #26071 from jai/patch-1 style(providers): update syntax for terraform >= 0.11	6 years ago
Alisdair McDiarmid	12241900d8	Update CHANGELOG.md	6 years ago
Alisdair McDiarmid	6d228cc560	Merge pull request #26036 from hashicorp/alisdair/output-empty-should-be-warning command: Warn instead of error for empty output	6 years ago
Alisdair McDiarmid	cf5dc8a5a5	Update CHANGELOG.md	6 years ago
Alisdair McDiarmid	89e8d0868a	Merge pull request #26061 from hashicorp/alisdair/013upgrade-registry-provider-redirect command: Add redirect support to 0.13upgrade	6 years ago
Jai Govindani	d8b36e5d12	style(providers): update syntax for terraform >= 0.11	6 years ago
Nick Fagerlund	f57861936c	website: fix a broken community provider link	6 years ago
Kristin Laemmert	49597c3c21	Update CHANGELOG.md	6 years ago
Kristin Laemmert	196c183dda	terraform: remove state from `validate` graph walk (#26063 ) This pull reverts a recent change to backend/local which created two context, one with and one without state. Instead I have removed the state entirely from the validate graph (by explicitly passing a states.NewState() to the validate graph builder). This changed caused a test failure, which (ty so much for the help) @jbardin discovered was inaccurate all along: the test's call to `Validate()` was actually what was removing the output from state. The new expected test output matches terraform's actual behavior on the command line: if you use -target to destroy a resource, an output that references only that resource is not removed from state even though that test would lead you to believe it did. This includes two tests to cover the expected behavior: TestPlan_varsUnset has been updated so it will panic if it gets more than one request to input a variable TestPlan_providerArgumentUnset covers #26035 Fixes #26035, #26027	6 years ago
Alisdair McDiarmid	fc7e467d19	command: Add redirect support to 0.13upgrade If a provider changes namespace in the registry, we can detect this when running the 0.13upgrade command. As long as there is a version matching the user's constraints, we now use the provider's new source address. Otherwise, warn the user that the provider has moved and a version upgrade is necessary to move to it.	6 years ago
Tony Carmichael	d7de46df10	Update publishing.html.md docs updates for GPG key gen instructions	6 years ago
Pam Selle	7032e651a8	Merge pull request #25927 from hashicorp/aug20_mirror_sidebar website: fix nav link text for 'providers mirror'	6 years ago
Pam Selle	8163c9771a	Merge pull request #25019 from 0zAND1z/patch-2 Update hashcode.go	6 years ago
Pam Selle	73cba31602	Merge pull request #25605 from davidair/patch-1 Tiny typo in an error message	6 years ago
Pam Selle	f2d213c461	Merge pull request #25657 from pdecat/typo_hierarchical Typo: heirarchical => hierarchical	6 years ago
Alisdair McDiarmid	2323e9370a	command: Warn instead of error for empty output When the output subcommand is called with no arguments, and there are no outputs to show, we previously rendered an error message but returned a non-error status code. This is confusing. This commit changes the text UI to use a warning diagnostic, which makes it clearer that this is a non-error situation. We do not change the exit code or the text of the warning, so hopefully this is not considered a breaking change.	6 years ago
Alisdair McDiarmid	27416fba92	Update CHANGELOG.md	6 years ago
Alisdair McDiarmid	8198e9758c	Merge pull request #26028 from hashicorp/alisdair/fix-eval-read-data-panic terraform: Fix createEmptyBlocks NestingSingle bug	6 years ago
Kristin Laemmert	3e1f741666	webside/docs: add note re: archive subdirectories to http download (#26020 ) section	6 years ago
Pam Selle	ba461fe0e1	Merge pull request #26004 from bzeitler69/patch-1 chore: Update mirror.html.md	6 years ago
Pam Selle	29af42df81	Merge pull request #25973 from Fabian-Schmidt/provisioner_comment_fix provisioner comment fix.	6 years ago
Pam Selle	233c7c6793	Run gofmt	6 years ago

1 2 3 4 5 ...

26598 Commits (efe78b2910c5b1f2292f0a16d990b2ad92352feb) All Branches Search

26598 Commits (efe78b2910c5b1f2292f0a16d990b2ad92352feb)

All Branches