255 Commits (f8fb61de12dea9ac94de3060a0d3e97ce9b5480b)

Author	SHA1	Message	Date
Sarah French	9b970d5454	chore: go get go.opentelemetry.io/otel/sdk@v1.43.0 & make syncdeps (#38366)	2 months ago
James Bardin	efa85192ef	PrepareComputedBlocks test	2 months ago
James Bardin	5410f9bd6a	objchange.PrepareComputedBlocks ... PrepareComputedBlocks nulls out any empty containers in a cty.Value corresponding to computed blocks, to indicate to the provider that the value is safe to insert a computed value into. TODO: do we really need this, or should the framework take care of it like it currently does already? - Doing this makes the protocol consistent that only null values can be replaced with computed values, but it's also more work that is currently redundant.	2 months ago
James Bardin	9ae47096ae	update objchange validations ... add computed block handling to AssertPlanValid and AssertObjectCompatible.	2 months ago
James Bardin	0f2503e4ea	detect non-legacy schemas ... We already had a heuristic for flagging non-legacy schemas in the blocktoattr fixup code, but now we need to extend that to computed blocks. Adapt these checks to the block schema type itself since we want to use the check outside of the old blocktoattr package.	2 months ago
Roniece	95c947e7f4	Add ActionInvocationFromProto, call actioninvocationFromTFPlan	3 months ago
Mutahhir Hayat	ab6119fd90	Revert fix and instead update test expectation	3 months ago
Mutahhir Hayat	581fd6d550	Fix test with incorrect provider address	3 months ago
Mutahhir Hayat	e074b103dd	Revert unncessary change to get provider address	3 months ago
Mutahhir Hayat	946918220c	Read Action invocations from planfile	3 months ago
Mutahhir Hayat	547473364c	Expose Action Invocation conversion to Proto publicly	3 months ago
Daniel Schmidt	188eeac4ff	remove now obsolete ReadConfig on planfile	3 months ago
Daniel Banck	297ebd989e	Move some planfile tests ... To be able to read and build the configuration in planfile related tests, we need methods from the `terraform` package. This commit moves the test into that package to make testing easier.	3 months ago
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.	3 months ago
Radek Simko	56c39007e2	make protobuf	3 months ago
Radek Simko	0fe906fa8c	make copyrightfix	3 months ago
Daniel Schmidt	d813ad14f7	add deprecation marks	4 months ago
Sarah French	fd7f25120b	PSS: Allow pluggable state store configuration to be read from a plan file (#37957) ... * feat: Allow reading state store configuration from a planfile and using it to prepare a Local backend that uses the state store * test: Assert that we can get and use state store configuration from a plan file * test: Add integration test showing that an apply command can use a plan file to configure and use a state store * test: Add E2E test showing pluggable state storage being used with the full init-plan-apply workflow * feat: A plan file will report the state storage provider among its required providers, if PSS is in use. See the code comment added in this commit. This addition does not impact an apply command as the missing provider will be detected before this code is executed. However I'm making this change so that the method is still accurate is being able to return a complete list of providers needed by the plan. * fix: Include error messages when there is a problem parsing provider or state store config when getting a backend from a planfile * feat: Add trace logs to BackendForLocalPlan indicating when the provider is launched and the state store is configured * chore: Small grammar change in error diagnostic * refactor: Remove suggestions when the plan's state store doesn't match the implementations in the provider * test: Add test coverage of what happens when the contents of a plan file using PSS doesn't match the resources available in the project	5 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>	6 months ago
Sarah French	9fb91c2229	PSS: Refactor Plan struct to reference `Backend` and `StateStore` via pointers, update calling code (#37946) ... * refactor: Update Plan struct's Backend field to be a pointer * fix: Add some refactorings or protections against nil pointers when accessing the Backend field on a Plan struct * refactor: Update Plan struct's StateStore field to be a pointer, update a nil check in calling code.	6 months ago
Sarah French	1dd8e60f15	chore: Bump golang.org/x/crypto dependency, ignore SA4003 linting errors globally (#37901) ... * chore: Upgrade golang.org/x/crypto - `go get golang.org/x/crypto@v0.44.0` * chore: Upgrade golang.org/x/crypto in submodules - `make syncdeps` * chore: Run `make generate` * chore: Ignore SA4003 linter error globally, as `golang.org/x/tools/cmd/stringer` generates code that breaks this rule when it's used with custom types that have unsigned integers or bytes as the underlying type.	6 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.	7 months ago
Liam Cervante	39d1293cf6	actions: consider event type when comparing action triggers (#37733)	8 months ago
Daniel Schmidt	e0748b30c4	add interface checks	8 months ago
Daniel Schmidt	7721cd5c50	refactor: make action diff transformer only responsible for attaching action invocations	8 months ago
Liam Cervante	898665193c	actions: disable support for deferrals (#37700)	8 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	8 months ago
Liam Cervante	49cc60531d	actions: fix cycle when multiple actions are triggered across multiple events (#37591)	9 months ago
James Bardin	1cb7d1859f	Merge pull request #37515 from hashicorp/jbardin/generate-config ... provider GenerateResourceConfig	9 months ago
Daniel Schmidt	ad4371342f	track partial expanded action invocations through deferred action invocation ... like we do it for resources just simpler because we don't have layered addrs maps	9 months ago
Daniel Schmidt	b2c4766d5e	implement review feedback	9 months ago
Daniel Schmidt	dffeeec81e	partially expand triggers as well	9 months ago
Daniel Schmidt	b6a9990354	deferring a dependency resource should defer action invocation	9 months ago
Daniel Schmidt	29b2ab15e2	support partial expansion in actions	9 months ago
James Bardin	4c610ac5e6	use the new genconfig types throughout	9 months ago
James Bardin	ddc47f15e7	remove the recursive genconfig resource struct ... The Resource struct didn't really match the data structure. Refactor this to make it easier to break up the config generation calls so we can pass in final config from the provider.	9 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	9 months ago
Daniel Schmidt	871d3ce64f	support sensitive values in action configuration	9 months ago
Daniel Schmidt	c36de59d41	handle providers deferring action invocations	9 months ago
Daniel Schmidt	14c83aa7ee	allow reporting action invocations as deferred	9 months ago
Daniel Schmidt	854232f443	add equals method to action invocation	9 months ago
Daniel Schmidt	5187efdd1d	refactor: move method into changes_src	9 months ago
Daniel Schmidt	219c31f4eb	action: move action trigger into nested struct ... this prepares the work on CLI / flag-driven invocations	9 months ago
James Bardin	7ed24d208a	make protobuf	10 months ago
Daniel Schmidt	cf98e0bc66	dont decode action invocations a second time	10 months ago
Daniel Schmidt	27e58b32ca	properly handle actions without config	10 months ago
Daniel Schmidt	1bd8eb8629	save config value to planfile	10 months ago
Daniel Schmidt	fb0445faf2	allow language experiments for terraform show	10 months ago
Daniel Schmidt	4fb4c3f056	render action config values	10 months ago
Daniel Schmidt	eb26b72d55	display lifecycle triggered actions aside their triggering resources	10 months ago