terraform

Commit Graph

Author	SHA1	Message	Date
Kristin Laemmert	70e074b8aa	chore (actions): rename LifecycleActionTrigger -> ResourceActionTrigger in plan and proto We'd previously removed all other references to "lifecycle" actions, which made this reference stand out. ResourceLifecycleActionTrigger is probably the most accurate name, but as this type just needs to be differentiated from InvokeActionTrigger I thought "resource" was enough (and I specifically wanted= to avoid lifecycle at all). I'm not super attached to the name, but I did think it would be clearer if we avoided Lifecycle as much as possible, since that's got some overlap with action subtypes. In this instance, we call it a LifecycleActionTrigger because it's come from the resource's `lifecycle` block. This doesn't directly relate to the concept of LifecycleActions - even if we expand the design to have multiple action types (for example generic and lifecycle actions), both those actions types would use this same Trigger struct.	2 months ago
Radek Simko	56c39007e2	make protobuf	2 months ago
Radek Simko	0fe906fa8c	make copyrightfix	2 months ago
Sarah French	f591872699	PSS: Allow pluggable state store configuration to be stored in a plan file (#37956 ) * refactor: Rename Meta's backendState field to backendConfigState This helps with navigating ambiguity around the word backend. The new name should indicate that the value represents a `backend` block, not a more general interpretation of what a backend is. * fix: Only set backendConfigState to synthetic object if it's nil due to a lack of data. Don't change it if pluggable state storage is in use. * feat: Enable recording a state store's details in an Operation, and using that data when creating a plan file. * fix: Include provider config when writing a plan file using pluggable state storage * fix: Having `backendConfigState` be nil may be valid, but it definitely isn't valid for `stateStoreConfigState` to be nil When backendConfigState is nil it means that an implied local backend is in use, i.e. there is no backend block in the config. * test: Add integration test showing that a plan command creates a plan file with the expected state_store configuration data * refactor: Apply suggestion from @radeksimko Co-authored-by: Radek Simko <radeksimko@users.noreply.github.com> * fix: Allow panics to occur if an unexpected implementation of `backend.Backend` is encountered when managing a state store * docs: Add code comment explaining the current situation with passing backend config state to downstream logic. In future this should be simplified, either via refactoring or changes affecting the implied local backend --------- Co-authored-by: Radek Simko <radeksimko@users.noreply.github.com>	4 months ago
Sarah French	2e5b5dee5d	Upgrade protoc and protoc-gen-go-grpc versions to matching terraform-plugin-go (#37647 ) * Update protoc version in downloader script * go get google.golang.org/grpc/cmd/protoc-gen-go-grpc v1.5.1 This matched terraform-plugin-go * make protobuf * Run `make protobuf` * Update generator to handle generic types from google.golang.org/grpc Looks like this was added in v1.69.3 in https://github.com/grpc/grpc-go/pull/7057 ? * Run `make generate` * Fix "cannot infer Res" compile error - more usage of generics * More fixing compile errors due to switching to use of a generic * Make putting `google.golang.org/grpc` import into generated files conditional * Run `make generate` * Update more places where generics now need to be used * Update generator to handle any types from google.golang.org/grpc in same switch case.	6 months ago
Kristin Laemmert	df113486a1	actions: remove references to action types, linked resources (#37616 ) * action renaming * actions: remove references to action types * actions: remove references to linked_resources or action types from the plan proto	7 months ago
Liam Cervante	866363ffff	actions: add invoke nodes to the graph (#37521 ) * actions: add invoke graph nodes * fix small bugs * add additional tests * remove whitespace * fix copyright headers * go generate * address comments	8 months ago
Daniel Schmidt	871d3ce64f	support sensitive values in action configuration	8 months ago
Daniel Schmidt	14c83aa7ee	allow reporting action invocations as deferred	8 months ago
Daniel Schmidt	219c31f4eb	action: move action trigger into nested struct this prepares the work on CLI / flag-driven invocations	8 months ago
James Bardin	7ed24d208a	make protobuf	8 months ago
Daniel Schmidt	eb26b72d55	display lifecycle triggered actions aside their triggering resources	9 months ago
Daniel Schmidt	2654e4d7cd	add information for graph building into plan action invocations	9 months ago
Kristin Laemmert	0374f04424	Add ValidateActionConfig to provider interface, protocol & internal implementations (#37345 ) * Add ValidateActionConfig to provider interface and protocol * Update internal/provider-simple-v6/provider.go Co-authored-by: Daniel Schmidt <danielmschmidt92@gmail.com> --------- Co-authored-by: Daniel Schmidt <danielmschmidt92@gmail.com>	9 months ago
Kristin Laemmert	9256074c43	Actions in plan/changes (#37320 ) * Add actions to the plans and change * jsonplan - ignoring LinkedResources for now, those are not in the MVP * pausing here: we'll work on the plan rendering later	9 months ago
Sarah French	2349481b23	Update data stored in plan files to enable using PSS with saved plans (#37246 ) * Implement `ForPlan` method on `StateStoreConfigState`, add `Planner` interface * Rename `ForPlan` method to `Plan` * Allow plan files to contain information about state stores * Add code needed for representing a state store in the Plan struct, which is used when handling plan files * Add ability to read/write either a backend or state store's data in a plan file. Add some test coverage. * Update plan's `ProviderAddrs` method to include the provider used for PSS, if present * Split interfaces * Apply feedback from code review * Refactor `SetVersion` to use appropriate constructor * Split `ProviderAddrs` method test into two * Fix method call after rename * Fix test * Remove change to `(p Plan) ProviderAddrs()` We may re-add this when we implement PSS for use during apply commands with plan files Remove changes to test, now that the plan doesn't report the provider used for PSS anymore.	10 months ago
James Bardin	a6ec17cb77	rename function results table Remove "provider" from the function results fields since it's not going to be exclusively used for providers any longer.	11 months ago
Daniel Banck	0aa4ce972d	Add resource identities to plan file and JSON output (#36903 )	12 months ago
Sarah French	6ef0498f9c	Update to Go 1.24.1, update dependencies (#36790 ) * go get github.com/hashicorp/go-azure-helpers@v0.72.0 * .go-version to 1.24.1 * Run `./scripts/syncdeps.sh` This propagates the Go version upgrade * gcs : go get google.golang.org/api@v0.155.0 * gcs: go mod tidy * Run `./scripts/syncdeps.sh` * make generate && make protobuf	1 year ago
Sarah French	a04664a2e5	Update `hashicorp/go-plugin` dependency (#36561 ) * go get github.com/hashicorp/go-plugin * ./scripts/syncdeps.sh * make protobuf	1 year ago
Daniel Schmidt	ceb52e65bb	stacks: support forgetting components	2 years ago
James Bardin	9ff727440e	udpate generated files	2 years ago
Liam Cervante	87bbc47737	stacks: include plan mode in stacks plan format (#35405 ) * stacks: include plan mode in stacks plan format * fix tests * fix missed files	2 years ago
Liam Cervante	96da5e9f46	deferred actinos: add support for unknown ids in import blocks (#35300 )	2 years ago
Martin Atkins	641219bd19	plans: Track input variables that must be re-supplied during apply We'll use this to track what subset of the ephemeral input variables were set in the planning options, and which ones must therefore be re-supplied in the apply phase options. This new plan field is not yet populated anywhere. The uses of this will follow in subsequent commits.	2 years ago
Liam Cervante	28797e7938	Add the deferred changes into the plan (#34946 ) * Add the deferred changes into the plan * add copywrite headers	2 years ago
Martin Atkins	d3b8a55781	go.mod: go get google.golang.org/protobuf@v1.33.0 Many of the changes between these two versions seem to be in parts of the library that Terraform doesn't use, but there are a few sensitive parts: - Slight changes to details of how the library implements the JSON encoding of protobuf. Terraform CLI/Core don't use this, but some of the backends might use it indirectly when talking to their underlying APIs. - Some details of the "protoreflect" package for working with protobuf descriptors dynamically (rather than using generated stubs) have changed, but it seems pretty marginal and unlikely to cause problems.	2 years ago
Martin Atkins	884e1fb2a4	terraform: Plans can be "complete" and "applyable" These ideas are both already implied by some logic elsewhere in the system, but until now we didn't have the decision logic centralized in a single place that could therefore evolve over time without necessarily always updating every caller together. We'll now have the modules runtime produce its own boolean ruling about each characteristic, which callers can rely on for the mechanical decision-making of whether to offer the user an "approve" prompt, and whether to remind the user after apply that it was an incomplete plan that will probably therefore need at least one more plan/apply round to converge. The "Applyable" flag directly replaces the previous method Plan.CanApply, with equivalent logic. Making this a field instead of a method means that we can freeze it as part of a saved plan, rather than recalculating it when we reload the plan, and we can export the field value in our export formats like JSON while ensuring it'll always be consistent with what Terraform is using internally. Callers can (and should) still use other context in the plan to return more tailored messages for specific situations they already know about that might be useful to users, but with these flags as a baseline callers can now just fall back to a generic presentation when encountering a situation they don't yet understand, rather than making the wrong decision and causing something strange to happen. That is: a lack of awareness of a new rule will now cause just a generic message in the UI, rather than incorrect behavior. This commit mostly just deals with populating the flags, and then all of the direct consequences of that on our various tests. Further changes to actually make use of these flags elsewhere in the system will follow in later commits, both in this repository and in other repositories.	2 years ago
James Bardin	bc945f22eb	Merge pull request #34515 from hashicorp/jbardin/provider-function-validation Add validation for provider function results	2 years ago
James Bardin	a3aa517589	store and verify provider functions calls in plan Store the hashed function calls within the plan file, so that Terraform can validate the results during apply as well. The error won't be as good, since we don't have access to the prior results to help debugging, but it is very helpful to indicate when a function returned an incorrect result rather than show that the resource attempted to apply a different value from what was originally planned.	2 years ago
Martin Atkins	a4d61733f6	stackplan: Include extra info in raw component instance plan We'll now track the planned action, the component addresses we depend on, and the planned output values.	2 years ago
kmoe	cc3e3bd513	planproto: add Forget, CreateThenForget actions (#34430 )	2 years ago
Martin Atkins	caeecbebcb	planfile: Move some of the proto convert funcs into package planproto Previously we had much of the mechanical conversion logic for going from in-memory structures to protobuf messages as unexported functions in the planfile package. We're now using planproto for parts of the representation of stack plans and states too, and so having those helpers exported is helpful. In some of our other protobuf packages we've adopted the convention of putting simple conversion functions in the same package as the protobuf stubs themselves, following the convention used upstream such as the additional encoding/decoding helper functions in the "anypb" package. This therefore follows that lead by adding some helpful constructor functions to package planproto and then making the equivalent functions back in planfile just thinly wrap them for now, to avoid churning the callers too much and thus making backports potentially harder.	2 years ago
Martin Atkins	9942deded1	plans: Move "planproto" up to toplevel The Go package containing the generated stubs for the plan file format's protobuf messages was previously nestled as an internal package under "plans", making it importable only for source files under "plans". To avoid duplicating various message types into the new "stack plan" serialization, we'll now make this package internal to the whole of this codebase rather than just to "plans", and then have the stack data protocol buffers schema import it to reuse the same message types.	2 years ago

34 Commits (add-missing-variable-loading)