terraform

Commit Graph

Author	SHA1	Message	Date
James Bardin	e29eb78cfd	decode change values with marks Marks stored in a plans.ChangeSrc were not decoded along with the stored values. This was working in many cases by evaluation correctly re-evaluating the marks, but this cannot happen in all cases.	5 years ago
Alisdair McDiarmid	4a93399c60	Merge pull request #28665 from hashicorp/alisdair/communicator-bastion-port-type communicator/ssh: Fix crash with SSH bastion port	5 years ago
Alisdair McDiarmid	fa676bde7c	core: Use number for port in connection schema This commit makes two changes to the provisioner connection block code: - Change the `port` argument type from string to number, which is technically more correct and consistent with `bastion_port`; - Use `uint16` as the struct member type for both ports instead of `int`, which gets us free range validation from the gocty package. Includes a test of the validation message when the port number is an invalid integer.	5 years ago
Martin Atkins	b402fd9d3a	command/views: Remove command-specific runningInAutomation We now have RunningInAutomation has a general concern in views.View, so we no longer need to specify it for each command-specific constructor separately. For this initial change I focused only on changing the exported interface of the views package and let the command-specific views go on having their own unexported fields containing a copy of the flag because it made this change less invasive and I wasn't feeling sure yet about whether we ought to have code within command-specific views directly access the internals of views.View. However, maybe we'll simplify this further in a later commit if we conclude that these copies of the flag are burdensome. The general version of this gets set directly inside the main package, which might at some future point allow us to make the command package itself unaware of this "running in automation" idea and thus reinforce that it's intended as a presentation-only thing rather than as a behavioral thing, but we'll save more invasive refactoring for another day.	5 years ago
Martin Atkins	bf396b5f1b	command/views: main View type aware if it's running in automation This "running in automation" idea is a best effort thing where we try to avoid printing out specific suggestions of commands to run in the main workflow when the user is running Terraform inside a wrapper script or other automation, because they probably don't want to bypass that automation. This just makes that information available to the main views.View type, so we can then make use of it in the implementation of more specialized view types that embed views.View. However, nothing is using it as of this commit. We'll use it in later commits.	5 years ago
Martin Atkins	6f68065326	website: Explicit example of for_each chaining between resources This pattern follows as a natural consequence of how for_each is defined, but I've noticed from community forum Q&A that newcomers often don't immediately notice the connection between what for_each expects as input and what a for_each resource produces as a result, so my aim here is to show a short example of that in the hope of helping folks see the link here and get ideas on how to employ the technique in other situations.	5 years ago
Martin Atkins	b38f3301d1	command/views: Remove baseState argument from plan-rendering views In practice the current implementation isn't actually using this, and if we need access to states in future we can access them in either the plan.PriorState or plan.PrevRunState fields, depending on which stage we want a state snapshot of.	5 years ago
Martin Atkins	0ee76b92b8	core: Update working state for resource instances in refresh-only mode Previously in refresh-only mode we were skipping making any updates to the working state at all. That's not correct, though: if the state upgrade or refresh steps detected changes then we need to at least commit _those_ to the working state, because those can then be detected by downstream objects like output values.	5 years ago
Martin Atkins	0f936b9d80	plans/planfile: Read state snapshots as part of reading a plan Our model for plans/planfile has unfortunately grown inconsistent with changes to our modeling of plans.Plan. Originally we considered the plan "header" and the planned changes as an entirely separate artifact from the prior state, but we later realized that carrying the prior state around with the plan is important to ensuring we always have enough context to faithfully render a plan to the user, and so we added the prior state as a field of plans.Plan. More recently we've also added the "previous run state" to plans.Plan for similar reasons. Unfortunately as a result of that modeling drift our ReadPlan method was silently producing an incomplete plans.Plan object, causing use-cases like "terraform show" to produce slightly different results due to the plan object not round-tripping completely. As a short-term tactical fix, here we add state snapshot reading into the ReadPlan function. This is not an ideal solution because it means that in the case of applying a plan, where we really do need access to the state _file_, we'll end up reading the prior state file twice. However, the goal here is only to heal the modelling quirk with as little change as possible, because we're not currently at a point where we'd be willing to risk regressions from a larger refactoring.	5 years ago
Alisdair McDiarmid	0cbe4d8efb	communicator/ssh: Fix crash with SSH bastion port The connection block schema defines the bastion_port argument as a number, but we were incorrectly trying to convert it from a string. This commit fixes that by attempting to convert the cty.Number to the int result type, returning the error on failure. An alternative approach would be to change the bastion_port argument in the schema to be a string, matching the port argument. I'm less sure about the secondary effects of that change, though.	5 years ago
Rachel Sharp	87c9e78666	Merge pull request #28604 from hashicorp/res-lifecycle-tutorial Add link to lifecycle tutorial	5 years ago
Alisdair McDiarmid	fb53259907	Merge pull request #28644 from hashicorp/alisdair/length-lookup-marks-fixes Improve marks support for `length` and `lookup`	5 years ago
Alisdair McDiarmid	dbe5272931	functions: Improve marks support for lookup Several changes to lookup to improve how we handle marked values: - If the entire collection is marked, preserve the marks on any result (whether successful or fallback) - If a returned value from the collection is marked, preserve the marks from only that value, combined with any overall collection marks - Retain marks on the fallback value when it is returned, combined with any overall collection marks - Include marks on the key in the result, as otherwise the result it ends up selecting could imply what the sensitive value was - Retain collection marks when returning an unknown value for a not wholly-known collection See also https://github.com/zclconf/go-cty/pull/98	5 years ago
James Bardin	3252df4b91	Merge pull request #28640 from hashicorp/jbardin/configload-diags Don't try to build the config if there were errors loading	5 years ago
James Bardin	ced676d50d	fixed configloader doesn't add unnecessary diags	5 years ago
Alisdair McDiarmid	e0c6b3fcda	functions: Improve marks support for length Similar to cty's implementation, we only need to preserve marks from the value itself, not any nested values it may contain. This means that taking the length of an umarked list with marked elements results in an unmarked number.	5 years ago
James Bardin	655f18c393	don't build a config if it didn't load properly	5 years ago
Martin Atkins	8d4d333efe	core: If we refresh during orphan processing, use the result for planning If we don't do this then we can create a situation where refresh detects that an object already doesn't exist but we plan to destroy it anyway, rather than returning "no changes" as expected.	5 years ago
James Bardin	ecd030eb26	Merge pull request #28624 from hashicorp/jbardin/schema-value-marks null check in ValueMarks	5 years ago
James Bardin	d76a8fcf6c	null check in ValueMarks	5 years ago
Alisdair McDiarmid	91cdde1d67	Merge pull request #28608 from hashicorp/alisdair/json-plan-replace-paths jsonplan: Add replace_paths	5 years ago
Martin Atkins	3443621227	core: Track both previous run state and refresh state during planning The "previous run state" is our record of what the previous run of Terraform considered to be its outcome, but in order to do anything useful with that we must ensure that the data inside conforms to the current resource type schemas, which might be different than the schemas that were current during the previous run if the relevant provider has since been upgraded. For that reason then, we'll start off with the previous run state set exactly equal to what was saved in the prior snapshot (modulo any changes that happened during a state file format upgrade) but then during our planning operation we'll overwrite individual resource instance objects with the result of upgrading, so that in a situation where we successfully run plan to completion the previous run state should always have a compatible schema with the "prior state" (the result of refreshing) for managed resources, and thus the caller can meaningfully compare the two in order to detect and describe any out-of-band changes that occurred since the previous run.	5 years ago
Martin Atkins	7c6e78bcb0	plans: Track both the previous run and prior states in the plan Until now we've not really cared much about the state snapshot produced by the previous Terraform operation, except to use it as a jumping-off point for our refresh step. However, we'd like to be able to report to an end-user whenever Terraform detects a change that occurred outside of Terraform, because that's often helpful context for understanding why a plan contains changes that don't seem to have corresponding changes in the configuration. As part of reporting that we'll need to keep track of the state as it was before we did any refreshing work, so we can then compare that against the state after refreshing. To retain enough data to achieve that, the existing Plan field State is now two fields: PrevRunState and PriorState. This also includes a very shallow change in the core package to make it populate something somewhat-reasonable into this field so that integration tests can function reasonably. However, this shallow implementation isn't really sufficient for real-world use of PrevRunState because we'll actually need to update PrevRunState as part of planning in order to incorporate the results of any provider-specific state upgrades to make the PrevRunState objects compatible with the current provider schema, or else our diffs won't be valid. This deeper awareness of PrevRunState in Terraform Core will follow in a subsequent commit, prior to anything else making use of Plan.PrevRunState.	5 years ago
Kristin Laemmert	5f30efe857	command tests: plan and init (#28616 ) * command/init: add test for reconfigure * command/plan: adding tests * command/apply: tests * command: show and refresh tests	5 years ago
James Bardin	1e3a60c7ac	Merge pull request #28606 from hashicorp/jbardin/providers-in-modules Validate passing default providers through modules	5 years ago
Alisdair McDiarmid	0ab7d901d9	Merge pull request #28607 from hashicorp/alisdair/cty-1.8.3 Upgrade cty to 1.8.3	5 years ago
Alisdair McDiarmid	b0f44fc293	go get github.com/zclconf/go-cty@v1.8.3	5 years ago
Alisdair McDiarmid	a5b7394f9a	command/jsonplan: Add replace_paths The set of paths which caused a resource update to require replacement has been stored in the plan since 0.15.0 (#28201). This commit adds a simple JSON representation of these paths, allowing consumers of this format to determine exactly which paths caused the resource to be replaced. This representation is intentionally more loosely encoded than the JSON state serialization of paths used for sensitive attributes. Instead of a path step being represented by an object with type and value, we use a more-JavaScripty heterogenous array of numbers and strings. Any practical consumer of this format will likely traverse an object tree using the index operator, which should work more easily with this format. It also allows easy prefix comparison for consumers which are tracking paths. While updating the documentation to include this new field, I noticed that some others were missing, so added them too.	5 years ago
James Bardin	168296b507	validate that modules name providers passed to mod Passing a provider into a module requires that it be named within the module. This would previously pass validation, however core would fail to resolve the provider resulting in an unclear "provider not found" error.	5 years ago
Rachel Sharp	c302fa507f	Add link to lifecycle tutorial	5 years ago
Alisdair McDiarmid	53fab10b26	Merge pull request #28598 from hashicorp/alisdair/fix-diagnostic-snippet-crash cli: Fix diagnostic snippet crash	5 years ago
Kristin Laemmert	3679de0630	command/format: fix repetitive "unchanged attribute hidden" message (#28589 ) writeNestedAttrDiff and writeAttrDiff were both printing the "unchanged attribute" message. This removes one of the redundant prints. Fixing this led me (in a very roundabout way) to realize that NestedType attributes were printing a sum total of unchanged attributes, including those in entirely unchanged elements, while not printing the total of unchanged elements. I added the necessary logic to count and print the number of unchanged elements for maps and lists.	5 years ago
Chris Arcand	5813620412	Merge pull request #28594 from hashicorp/go-tfe-update Update go-tfe client to v0.14.0	5 years ago
Alisdair McDiarmid	25f99857cf	cli: Fix crash with invalid JSON diagnostics If a JSON diagnostic value has a highlight end offset which is before the highlight start offset, this would previously panic. This commit adds a normalization step to prevent the crash.	5 years ago
Alisdair McDiarmid	3a9b369b43	views/json: Fix diag crash with invalid highlight Some diagnostic sources (I'm looking at you, HCL) fail to set the end of the subject range. This is a bug in those code paths, but we can ensure that we generate valid JSON diagnostics by checking for it here. By doing so before the range normalization, we ensure that we generate a unit width highlight whenever possible, so that at least something useful is displayed.	5 years ago
Alisdair McDiarmid	e9c9092c40	Fix missing trailing newline	5 years ago
Chris Arcand	2756f5ed08	Update Terraform Cloud/Enterprise client to v0.14.0	5 years ago
Martin Atkins	c63c06d3c4	core: -replace to emit only one warning for incomplete address If the user gives an index-less address for a resource that expects instance keys then previously we would've emitted one error per declared instance of the resource, which is overwhelming and not especially helpful. Instead, we'll deal with that check prior to expanding resources into resource instances, and thus we can report a single error which talks about all of the instances at once. This does unfortunately come at the expense of splitting the logic for dealing with the "force replace" addresses into two places, which will likely make later maintenance harder. In an attempt to mitigate that, I've included a comment in each place that mentions the other place, which hopefully future maintainers will keep up-to-date if that situation changes.	5 years ago
Martin Atkins	1d3e34e35e	command: New -replace=... planning option This allows a similar effect to pre-tainting an object but does the action within the context of a normal plan and apply, avoiding the need for an intermediate state where the old object still exists but is marked as tainted. The core functionality for this was already present, so this commit is just the UI-level changes to make that option available for use and to explain how it contributed to the resulting plan in Terraform's output.	5 years ago
James Bardin	f738246a03	add default provider nodes to root modules If a root modules declares a required_provider but has no configuration, add a graph node for the provider as if there were an empty configuration. This will allow the provider to be referenced by name in module call provider maps, so that a module can pass a default provider by name to a submodule. Normally these nodes are added by the MissingProviderTransformer, but they need to be in place earlier to resolve any possible "proxy provider nodes" within modules.	5 years ago
Alisdair McDiarmid	7f39f19ec7	Merge pull request #28584 from hashicorp/alisdair/add-reason-to-json-planned-change command/views: Add reason to JSON planned change	5 years ago
Alisdair McDiarmid	48b9055e42	Merge pull request #28583 from hashicorp/alisdair/sensitive-attribute-forces-replacement cli: Show forces replacement for sensitive attrs	5 years ago
Alisdair McDiarmid	7b23fa7877	command/views: Add reason to JSON planned change Now that we have extra information about the reason for a given resource action, include that in the JSON log output for planned changes.	5 years ago
Alisdair McDiarmid	c95e9ada6b	cli: Show forces replacement for sensitive attrs When rendering a plan diff, sensitive resource attributes would previously omit the "forces replacement" comment, which can lead to confusion when the only reason for a resource being replaced is a sensitive attribute.	5 years ago
Martin Atkins	6bed3008a5	website: Reworking of the "terraform plan" docs, and related pages It's been a long time since we gave this page an overhaul, and with our ongoing efforts to make plan and apply incorporate all of the side-effects that might need to be done against a configuration it seems like a good time for some restructuring in that vein. The starting idea here is to formally split the many "terraform plan" options into a few different categories: - Planning modes - Planning options - Other options The planning modes and options are the subset that are also accepted by "terraform apply" when it's running in its default mode of generating a plan and then prompting for interactive approval of it. This then allows us to avoid duplicating all of that information on the "terraform apply" page, and thus allows us to spend more words discussing each of them. This set of docs is intended as a fresh start into which we'll be able to more surgically add in the information about -refresh-only and -replace=... once we have those implemented. Consequently there are some parts of this which may seem a little overwraught for what it's currently describing; that's a result of my having prepared this by just deleting the -refresh-only and -replace=... content from our initial docs draft and submitted the result, in anticipation of re-adding the parts I've deleted here in the very near future in other commits.	5 years ago
Alisdair McDiarmid	95b86bf7ad	Merge pull request #28566 from hashicorp/alisdair/json-logs-operations-commands cli: Add JSON logs for operations commands	5 years ago
Martin Atkins	06adc69e2c	plans: Plan.Mode is now Plan.UIMode This is to make it more obvious at all uses of this field that it's not something to be used for anything other than UI decisions, hopefully prompting a reader of code elsewhere to refer to the comments to understand why it has this unusual prefix and thus see what its intended purpose is.	5 years ago
Martin Atkins	b37b1beddd	core: Minimal initial implementation of -replace=... option This only includes the internal mechanisms to make it work, and not any of the necessary UI changes to "terraform plan" and "terraform apply" to activate it yet. The force-replace options are ultimately handled inside the NodeAbstractResourceInstance.plan method, at the same place we handle the similar situation of the provider indicating that replacement is needed, and so the rest of the changes here are just to propagate the settings through all of the layers in order to reach that point.	5 years ago
Martin Atkins	1b464e1e9a	core: Minimal initial implementation of "refresh only" planning mode This only includes the core mechanisms to make it work. There's not yet any way to turn this mode on as an end-user, because we have to do some more work at the UI layer to present this well before we could include it as an end-user-visible feature in a release. At the lowest level of abstraction inside the graph nodes themselves, this effectively mirrors the existing option to disable refreshing with a new option to disable change-planning, so that either "half" of the process can be disabled. As far as the nodes are concerned it would be possible in principle to disable _both_, but the higher-level representation of these modes prevents that combination from reaching Terraform Core in practice, because we block using -refresh-only and -refresh=false at the same time.	5 years ago
Sam Velie	5d04c4ea27	docs: correct spelling of normally (#28508 )	5 years ago

1 2 3 4 5 ...

28190 Commits (e29eb78cfddfb1cd7f477457d6aedbcb8286fc4c) All Branches Search

28190 Commits (e29eb78cfddfb1cd7f477457d6aedbcb8286fc4c)

All Branches