terraform

Commit Graph

Author	SHA1	Message	Date
Pam Selle	aa044bdd39	Fix docs for 0.15 for vendor provisioners	5 years ago
Alisdair McDiarmid	30126baff4	Merge pull request #27199 from hashicorp/alisdair/remote-backend-version-latest backend/remote: Fix for "latest" workspace version	5 years ago
Alisdair McDiarmid	94e2fe9a38	Merge pull request #27197 from hashicorp/alisdair/terraform-remote-state-version-fix Fix terraform_remote_state backend version check	5 years ago
Alisdair McDiarmid	6e0d8cde91	backend/remote: Fix for "latest" workspace version Terraform Cloud/Enterprise support a pseudo-version of "latest" for the configured workspace Terraform version. If this is chosen, we abandon the attempt to verify the versions are compatible, as the meaning of "latest" cannot be predicted. This affects both the StateMgr check (used for commands which execute remotely) and the full version check (for local commands).	5 years ago
Alisdair McDiarmid	107dc0c34f	Fix terraform_remote_state backend version check The change recently introduced to ensure that remote backend users do not accidentally upgrade their state file needs to be disabled for all read-only uses, including the builtin terraform_remote_state data source.	5 years ago
Kristin Laemmert	93c36e67b1	terraform: refactor ReadData (#27189 ) I took some lessons learned during yesterday's marathon refactoring and re-refactored the dataSource plan and apply to be functions on NodeResourceAbstractInstance. Includes mild renaming to differentiate between plan and planDataSource.	5 years ago
Pam Selle	c2a143bb78	Merge pull request #27178 from hashicorp/deps/hcl2 Update hcl2 dependency	5 years ago
Hyunsuk Shin	16f8baa40e	Update setproduct.html.md (#27184 ) fill wrong syntax	5 years ago
Kristin Laemmert	e7aaf9e39f	Eval() Refactor: Plan Edition (#27177 ) * terraforn: refactor EvalRefresh EvalRefresh.Eval(ctx) is now Refresh(evalRefreshReqest, ctx). While none of the inner logic of the function has changed, it now returns a states.ResourceInstanceObject instead of updating a pointer. This is a human-centric change, meant to make the logic flow (in the calling functions) easier to follow. * terraform: refactor EvalReadDataPlan and Apply This is a very minor refactor that removes the (currently) redundant types EvalReadDataPlan and EvalReadDataApply in favor of using EvalReadData with a Plan and Apply functions. This is in effect an aesthetic change; since there is no longer an Eval() abstraction we can rename functions to make their functionality as obvious as possible. * terraform: refactor EvalCheckPlannedChange EvalCheckPlannedChange was only used by NodeApplyableResourceInstance and has been refactored into a method on that type called checkPlannedChange. * terraform: refactor EvalDiff.Eval EvalDiff.Eval is now a method on NodeResourceAbstracted called Plan which takes as a parameter an EvalPlanRequest. Instead of updating pointers it returns a new plan and state. I removed as many redundant fields from the original EvalDiff struct as possible. * terraform: refactor EvalReduceDiff EvalReduceDiff is now reducePlan, a regular function (without a method) that returns a value. * terraform: refactor EvalDiffDestroy EvalDiffDestroy.Eval is now NodeAbstractResourceInstance.PlanDestroy which takes ctx, state and optional DeposedKey and returns a change. I've removed the state return value since it was only ever returning a nil state. * terraform: refactor EvalWriteDiff EvalWriteDiff.Eval is now NodeAbstractResourceInstance.WriteChange. * rename files to something more logical * terrafrom: refresh refactor, continued! I had originally made Refresh a stand-alone function since it was (obnoxiously) called from a graphNodeImportStateSub, but after some (greatly appreciated) prompting in the PR I instead made it a method on the NodeAbstractResourceInstance, in keeping with the other refactored eval nodes, and then built a NodeAbstractResourceInstance inside import. Since I did that I could also remove my duplicated 'writeState' code inside graphNodeImportStateSub and use n.writeResourceInstanceState, so double thanks! * unexport eval methods * re-refactor Plan, it made more sense on NodeAbstractResourceInstance. Sorry * Remove uninformative `Eval`s from EvalReadData, consolidate to a single file, and rename file to match function names. * manual rebase	5 years ago
Martin Atkins	776b33db32	website: Recommend against making JSON/YAML with heredocs This is a repeated cause of confusion and questions in the community forum, because both JSON and YAML valid syntax are hard to generate using just string concatenation. Terraform has built-in functions for both of these common serializations to avoid those problems, and so this will hopefully make these better alternatives more discoverable.	5 years ago
Martin Atkins	ab1dd87540	website: Elaborate the "expressions" sub-pages in the language section When we did the earlier documentation rework for Terraform v0.12 we still had one big "Expressions" page talking about the various operators and constructs, and so we had to be a bit economical with the details about some more complicated constructs in order to avoid the page becoming even more overwhelming. However, we've recently reorganized the language documentation again so that the expressions section is split across several separate pages, and that gives some freedom to go into some more detail about and show longer examples for certain features. My changes here are not intended to be an exhaustive rewrite but I did try to focus on some areas I've commonly seen questions about when helping in the community forum and elsewhere, and also to create a little more connectivity between the different content so readers can hopefully find what they are looking for more easily when they're not yet sure what terminology to look for.	5 years ago
James Bardin	627a2121b8	Merge pull request #27174 from hashicorp/jbardin/ignore-unknown ignore_changes can ignore unknowns too	5 years ago
Pam Selle	52da8b6074	Update hcl2 dependency	5 years ago
Pam Selle	1db33b7ec7	Merge pull request #27169 from hashicorp/pselle/get-plugins Update docs and add warning for -get-plugins	5 years ago
Pam Selle	b963ea8594	Update docs and add warning for -get-plugins As of Terraform 0.13+, the get-plugins command has been superceded by new provider installation mechanisms, and general philosophy (providers are always installed, but the sources may be customized). Updat the init command to give users a warning if they are setting this flag, to encourage them to remove it from their workflow, and update relevant docs and docstrings as well	5 years ago
James Bardin	ee52f26647	ignore_changes can ignore unknowns too The logic for handling unknown equality was incorrect, and would miss changes where the configuration is still not known during plan.	5 years ago
Kristin Laemmert	bedc08f5eb	terraform: refactor EvalWriteStateDeposed (#27149 ) * terraform: refactor EvalWriteStateDeposed EvalWriteStateDeposed is now NodeDestroyDeposedResourceInstanceObject.writeResourceInstanceState. Since that's the only caller I considered putting the logic directly inline, but things are clunky enough right now that I think this is good enough for this refactor.	5 years ago
Pam Selle	ae025248cc	Merge pull request #27131 from hashicorp/pselle/double-marks Avoid double-marking variables	5 years ago
Pam Selle	12b5d437da	Avoid double-marking variables It is possible, say with multiple layers of sensitive variables, to "double-mark" a variable. Add a check to ensure this does not happen.	5 years ago
James Bardin	3b4079d451	Merge pull request #27141 from hashicorp/jbardin/ignore_changes Fixes for ignore_changes with unintended provider behavior	5 years ago
Kristin Laemmert	29d89c4a15	Eval(): refactor EvalWriteState() (#27145 ) * fix inaccurate log * terraform: refactor EvalWriteState EvalWriteState is refactored into a method on NodeAbstractResourceInstance and renamed writeResourceInstanceState. Import, my nemesis, gave me pause. I did not expect to find EvalWriteState in an transform node, and so I decided to copy the function inline rather than rethink my entire refactor for one function that's likely to be (heavily) refactored in the future.	5 years ago
Pam Selle	0c0ea09546	Merge pull request #27134 from tillepille/patch-1 documentation: fix small typo	5 years ago
James Bardin	b831039cf8	update CHANGELOG.md	5 years ago
Kristin Laemmert	7370a98ab7	Eval() Refactor (#27087 ) * terraform: refactor EvalPreApply and EvalPostApply EvalPreApply and EvalPostApply have been refactored as methods on NodeAbstractResourceInstance. * terraform: remove EvalReadState and EvalReadStateDeposed These two functions had already been re-implemented as functions on NodeAbstractResource, so this commit finished the process of removing the Evals and refactoring the tests. * terraform: remove EvalRefreshLifecycle EvalRefreshLifecycle was only used in one node, NodePlannableResourceInstance, so the functionality has been moved directly inline. * terraform: remove EvalDeposeState EvalDeposeState was only used in one function, so it has been removed and the logic placed in-line in NodeApplyableResourceInstance.managedResourceExecute. * terraform: remove EvalMaybeRestoreDeposedObject EvalMaybeRestoreDeposedObject was only used in one place, so I've removed it in favor of in-line code.	5 years ago
James Bardin	4f4e8c17e0	validate the configuration before ignore_changes The ignore_changes option `all` can cause computed attributes to show up in the validation configuration, which will be rejected by the provider SDK. Validate the config before applying the ignore_changes options. In the future it we should probably have a way for processIgnoreChanges to skip computed values based on the schema. Since we also want a way to more easily query the schema for "computed-ness" to validate the ignore_changes arguments for computed values, we can fix these at the same time with a future change to configschema. This will most likely require some sort of method to retrieve info from the configschema.Block via cty.Path, which we cannot easily do right now.	5 years ago
James Bardin	02e7efab9e	re-apply ignore_changes after plan for legacy Because we allow legacy providers to depart from the contract and return changes to non-computed values, the plan response may have altered values that were already suppressed with ignore_changes. A prime example of this is where providers attempt to obfuscate config data by turning the config value into a hash and storing the hash value in the state. There are enough cases of this in existing providers that we must accommodate the behavior for now, so for ignore_changes to work at all on these values, we will revert the ignored values once more on the planned state.	5 years ago
Alisdair McDiarmid	6bacc7a73c	Merge pull request #27128 from hashicorp/alisdair/sensitivity-change-permadiff terraform: Write state if sensitivity changes	5 years ago
Dmitry Tokarev	8d1c416a53	website: Fix link to external documentation "Git URLs"	5 years ago
James Bardin	aa5c8add2e	fix bug in ignore_changes Transform The cty.Transform for ignore_changes could return early when building a map that had multiple ignored keys. Refactor the function to try and separate the fast-path a little better, and hopefully make it easier to follow.	5 years ago
Alisdair McDiarmid	50f4d79867	terraform: Write state if sensitivity changes When applying, we return early if only sensitivity changed between the before and after values of the changeset. This avoids unnecessarily invoking the provider. Previously, we did not write the new value for a resource to the state when this happened. The result was a permanent diff for resource updates which only change sensitivity, as the apply step is skipped and the state is unchanged. This commit adds a state write to this shortcut return path, and fixes a test for this exact case which was accidentally relying on a value diff caused by an incorrect manual state value.	5 years ago
Petros Kolyvas	2ce71ab43c	Upgrade guide link fix (#27124 )	5 years ago
Masayuki Morita	93b6f15c9d	website: Fix typo in docs/commands/cli-config (#27038 )	5 years ago
Petros Kolyvas	20a5db1c86	Website: 0.14 Upgrade guide additions (#27112 ) * Update 0-14.html.markdown Spelling again. Thanks @pselle	5 years ago
Nick Fagerlund	0c0749edcf	website: Fix several broken links (#27091 )	5 years ago
Martin Atkins	323cd4364b	website: Correct formatting for lists in dependency lock docs I originally drafted these docs in a context where I was relying on GitHub's Markdown renderer, and carelessly imported them into the Terraform website without verifying that the website's Markdown renderer could process it. This particular quirk has bitten us before: the website Markdown parser expects follow-on paragraphs in a list item to be indented at least four spaces, and with less than that it ignores the leading whitespace altogether and just understands a normal paragraph. This change will cause the follow-on paragraphs to now correctly render as part of the bullet points they are intended to be attached to.	5 years ago
Mark Lewis	9935138e1c	Update for_each.html.md minor grammar improvement.	5 years ago
Mark Lewis	ffea7a4cda	Update for_each.html.md	5 years ago
Tim Schrumpf	e102465e91	fix small typo	5 years ago
Connor Osborn	2c2ed53ff3	Fix apt install typo (#27074 ) Apt install expects a `name=version` NOT `name==version`	5 years ago
Petros Kolyvas	5cb2d4894c	Anytrue alltrue docs clarification. (#27108 ) * Anytrue alltrue docs clarification. * Update alltrue.html.md I can't spell. * Update anytrue.html.md Yes, I can't spell.	5 years ago
Nick Fagerlund	2119510669	Merge pull request #27089 from hashicorp/dec20_release_fixes_upstream_version website: fix a few functional glitches	5 years ago
Nick Fagerlund	cca1bc91c3	website: fix bad layout in defaults function page This layout no longer exists.	5 years ago
Nick Fagerlund	5cff04b3ab	website: fix malformed yaml in a few function pages	5 years ago
James Bardin	b0ce552c90	Merge pull request #27088 from hashicorp/jbardin/un-legacy don't use legacy import for the terraform.UIInput interface	5 years ago
James Bardin	dd5dae27f8	don't use legacy import for the UIInput interface The import was switch for other types which has since been removed. Point this at the correct package.	5 years ago
James Bardin	dcf0dba6f4	Merge pull request #27081 from hashicorp/jbardin/staticcheck Fixes to pass static analysis	5 years ago
Kristin Laemmert	3fa063b8dc	command/format: concise diff is now the default (#27079 ) * command/format: concise diff is no longer an experiment Since state formatting goes through the "diff" printer, I have repurposed the concise flag as a verbose flag, used only when printing state. It's silly but it works! * remove helper/experiment With this experiment concluded, we no longer need helper/experiment. The shadow experiment had not been touched in many years, so I removed all references, and removed the package entirely. Any new experiments are expected to be configuration experiments handled by our (other) experiments package. * check for the verbose flag consistently, in case we end up using it in plans in the future	5 years ago
James Bardin	6529659455	internal/providercache: staticcheck	5 years ago
James Bardin	313d3e5c4d	builtin/provisioners/remote-exec: staticcheck	5 years ago
James Bardin	0b4c96fa92	command/jsonprovider: staticcheck	5 years ago

1 2 3 4 5 ...

27506 Commits (aa044bdd3974056be01bfacd1a2000486fabc76b) All Branches Search

27506 Commits (aa044bdd3974056be01bfacd1a2000486fabc76b)

All Branches