4161 Commits (prototype-migrate-ux)

Author	SHA1	Message	Date
Daniel Schmidt	c16203700f	feat: add interactive TUI migration selector to migrate run ... When `terraform migrate run` is called without a migration ID, it scans for applicable migrations and presents an interactive selector with arrow keys, space to toggle, enter to confirm. Supports: arrow keys, j/k (vim), space (toggle), a (toggle all), enter (confirm), q (cancel).	3 months ago
Daniel Schmidt	83b8bbd4ef	fix: remove duplicate subcommand list from migrate help ... Let the CLI framework auto-generate the subcommand list instead of duplicating it in our custom help text.	3 months ago
Daniel Schmidt	c7498f3efd	refactor: rename migrate apply to migrate run subcommand ... Changes the command structure from: terraform migrate <id> to: terraform migrate run <id> This gives a clearer UX with two explicit subcommands: terraform migrate list — list available migrations terraform migrate run — run a specific migration	3 months ago
Daniel Schmidt	21432988d7	feat: make migration engine scan .tf files recursively ... Enables migrations to work across nested directory structures (e.g. modules/).	3 months ago
Daniel Schmidt	8cea21ac5e	feat: polish diff output, fix -no-color, fix step mode prompts ... - Improve diff rendering with context lines and ... separators - Fix -no-color flag not propagating to views - Fix step mode consuming all stdin at once by using persistent scanner - Show red/green colored diff lines with proper context	3 months ago
Daniel Schmidt	7387e5dde4	Improve diff output to show context lines around changes ... The Diff method now shows up to 3 lines of context before and after each change, with "..." separators between non-adjacent hunks. This makes the output much easier to read, similar to standard unified diff.	3 months ago
Daniel Schmidt	4acb2d3bdc	feat: register migrate commands and fix argument ordering ... Register "migrate" and "migrate list" in the commands map. Fix argument parser to allow flags before or after the migration ID, since Go's flag package stops at the first non-flag argument.	3 months ago
Daniel Schmidt	35e69e685e	fix: remove unused parameter in step method	3 months ago
Daniel Schmidt	062034180d	Add terraform migrate command, list subcommand, and apply subcommand ... Implements the three command files for the migrate feature: - migrate_command.go: Parent command that shows help or delegates to apply when first arg contains "/" (migration ID shorthand) - migrate_list.go: Lists available migrations for the current working directory by scanning .tf files against all registered migrations - migrate_apply.go: Applies a specific migration with three modes: default (apply all), dry-run (show diffs without writing), and step (interactive) Includes tests for list (with/without matches) and apply (default, dry-run, not-found, no-changes).	3 months ago
Daniel Schmidt	f3f273879f	fix: replace interface{} with any in migrate views	3 months ago
Daniel Schmidt	e3f3b72177	Add views for terraform migrate list and apply commands ... Implements MigrateList and MigrateApply view interfaces with both Human and JSON implementations following existing view patterns. Includes LCS-based diff rendering for dry-run output.	3 months ago
Daniel Schmidt	9ef826d1dd	Add argument parsing for migrate list and migrate apply commands ... Introduces ParseMigrateList and ParseMigrateApply functions following existing argument parsing patterns. MigrateList supports -detail and -json flags. MigrateApply supports -dry-run, -step, and -json flags with a required migration ID positional argument validated as namespace/provider/name format.	3 months ago
Daniel Schmidt	8a5a9de378	Add migration engine with Apply and WriteResults functions ... Implement the migration engine that applies migrations to .tf files in a directory. Apply scans for .tf files, chains sub-migrations so each sees the output of the previous one, and returns results without writing to disk. WriteResults writes the final state of changed files.	3 months ago
Daniel Schmidt	c8c313ee7f	fix: clean up string concatenation in terraform migrations	3 months ago
Daniel Schmidt	9935102956	Implement sample migrations for AWS, Azure, and Terraform Core ... Add regex-based Apply functions for all sample migrations: - AWS v3-to-v4: s3-bucket-acl, s3-bucket-cors, s3-bucket-logging - Azure v3-to-v4: subnet-delegation, network-security-rule - Terraform v1.x-to-v2.x: required-providers-map, backend-to-cloud Includes shared helpers for nested block extraction/manipulation and table-driven tests for each sub-migration with positive and no-op cases.	3 months ago
Daniel Schmidt	f00299310b	Add migrate package with core types, registry, and provider stubs ... Introduce the foundation for `terraform migrate`: Migration and SubMigration types, a Registry with All()/Find() methods, stub migration files for aws/azurerm/terraform, and initial tests.	3 months ago
Daniel Banck	02723fcd79	Add variable arguments to init help text	3 months ago
Daniel Schmidt	2077b53936	add tests for dynamic module sources in stacks	3 months ago
Daniel Banck	6f8592eee4	Make dynamic reference error message more precise	3 months ago
Daniel Banck	ee8f7abc04	Add snapshot-related test for the new graph-based config loader ... This ensures we test snapshot related configuration loading. These tests previously lived in the `configload` package.	3 months ago
Daniel Banck	45ba6796ba	Add more dynamic module sources tests	3 months ago
Daniel Banck	b6804e2edd	Use configuration values for jsonconfig ... Instead of outputting the raw values from the ModuleCall, we're now using the evaluated values from the Config. This should keep the JSON output unchanged, we just need to make sure to persist the values in `Config` when loading the configuration.	3 months ago
Daniel Banck	55198eb221	Feedback: Rename remaining static -> const	3 months ago
Daniel Banck	834c2f4c21	Fix modules command ... To be able to show version constraint from modules, we now store them during configuration loading.	3 months ago
Daniel Banck	5a70c424b3	Fix import and show command ... This commit moves some code around to fix configuration loading during the (legacy) import command. And add vars to the show command.	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
Daniel Banck	0043e1ce24	Update module call configuration storage ... This turns the string representation of the source and version attribute of a module call into an expression. This leads to a change in the JSON output: `"source": "./foo"` --> `"source": {"constant_value": "./foo"},`	3 months ago
Daniel Banck	d5d12cdd49	Treat most values as dynamic during init walk ... Since init only really cares about references that are used inside a module source (or version), we can treat all other references as dynamic/unknown and shortcut most of their validation steps.	3 months ago
Daniel Banck	4ef9684188	Rework most of the configuration loading ... We previously used a loader -> BuildConfig flow to load configuration. This commit changes most (but not all yet) flows to use the new graph-based approach. Instead of simply recursively loading the modules, we now need to take a stepped approach: 1. Load the root module 2. Collect the variables and their values 3. Build the configuration with the graph-based approach Because this approach relies on different parts from different packages, it can't easliy be done within the `configload` package. So, now we do most of in the backend or command.	3 months ago
Daniel Banck	fb60c15670	Update init to use new graph-based workflow ... The init command and the module installer are now using the new graph-based workflow to install modules instead of using the recursive BuildConfig.	3 months ago
Daniel Banck	11d819048a	Store module source and version expressions ... Instead of evaluating and parsing a module source and version on configuration loading, we now simply store the expression. Decoding is now done during the graph-based configuration loading in the module install node.	3 months ago
Daniel Banck	28b76c1105	Introduce a new init graph ... The new init graph builder creates a small graph that can be used to install or load module configuration. It reuses different walkers to either install modules or validate the manifest during configuration loading. The new module install node dynamically expands the graph after module installation with a subgraph for the installed module.	3 months ago
Radek Simko	7127c76b04	command/views: Bump UI version to v1.3 (#38231)	3 months ago
Radek Simko	07b3e3b800	command/init: Merge duplicated PSS logic back into existing codepath (#38227)	3 months ago
Mutahhir Hayat	2bb747222b	Update copyright for conversion_test.go	3 months ago
Mutahhir Hayat	71f0afc644	Include trigger information in progress messages ... This disambiguates multiple invocations of the same action instance (see this excellent comment by @DanielMSchmidt for a better overview (https://github.com/hashicorp/terraform/pull/38051/changes#r2812460131)	3 months ago
Mutahhir Hayat	551bf42090	Add Action Invocations in ComponenentInstanceChanges	3 months ago
Roniece	a38c47ae72	Add ActionInvocationStatus, ActionInvocationProgress messages	3 months ago
Mutahhir Hayat	7aa0a71078	Create Protobuf changes for stack planning that includes Action invocations	3 months ago
James Bardin	7960f60d21	Merge pull request #38160 from hashicorp/jbardin/inline-type-conversion ... inline type conversions	3 months ago
Sebastian Rivera	305dba5dcc	feat: denote sensitive attribute paths in query start msg ... This new field will be consumed in order to redact sensitive values referenced in a list block's input configuration from the query logs. We simply pipe the config schema and the marked values, and include the paths in the query_start log output.	3 months ago
Kristin Laemmert	0ce1ae7cd6	Merge pull request #38204 from hashicorp/mildwonkey/action-prep ... simplifying actions prep - renaming action-related node types and some internal fields.	3 months ago
Radek Simko	cd9257cd53	PSS: Enable state store configuration change (#38153)	3 months ago
Sarah French	c37cf1c0f5	test: Enable assertions about prompt text shown to users (#38212) ... * test: Update `testInputMap` and `(*UIInput) Input` to allow making assertions about what prompts a user has been shown. Make cleanup happen inside the helper. * test: Update test to assert about prompt contents, showing how changes to `testInputMap` can be used * docs: update godoc for testInputMap	3 months ago
Sarah French	9f5f21f1d8	test: Enable mocking http provider sources in tests (#38206) ... * test: Update`MockSource` to be able to present providers as being installed via HTTP, add `newMockProviderSourceViaHTTP` for direct use in tests. Compare newMockProviderSourceViaHTTP to the existing newMockProviderSource. newMockProviderSource uses FakeInstallablePackageMeta, which creates metadata for providers that says it's being sourced from a local archive. In newMockProviderSourceViaHTTP the metadata reports the provider is downloaded via HTTP. The URL is created using a base URL that should be obtained from a test http server created in the test. * test: Add `newMockProviderSourceUsingTestHttpServer` helper, to abstract away making the http test server. Add test showing it in use. * refactor: Update test helpers to call t.Cleanup internally	3 months ago
Daniel Schmidt	2424cf6423	make test case more robust to developer environments	4 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.	4 months ago
Kristin Laemmert	a5dade523b	renaming action-related nodes	4 months ago
Daniel Banck	a39e3bce32	make syncdeps	4 months ago
Daniel Schmidt	905845f363	copy rename	4 months ago