Skip to content

Showcasing Config Difference Between Creating A New Project Vs Existing Project For Creation Of Migration Stack#5

Open
sujaysamanta wants to merge 2 commits intostack-projects-test-new-v1from
stack-projects-test-existing-v1
Open

Showcasing Config Difference Between Creating A New Project Vs Existing Project For Creation Of Migration Stack#5
sujaysamanta wants to merge 2 commits intostack-projects-test-new-v1from
stack-projects-test-existing-v1

Conversation

@sujaysamanta
Copy link
Contributor

This pull request updates the Terraform configuration for the stacks migration infrastructure, primarily focusing on project and stack naming, and introduces an import block for a specific project resource. These changes help clarify environment identification and enable resource management for an existing project.

Project and stack configuration updates:

  • Changed the default value of the project_name variable to "Tf-Migrate-Stack-Migration-Retry-Test" in stacks_migration_infra/variables.tf to better reflect the purpose of the migration environment.
  • Updated the default value of the stack_name variable to "hello-stacks-v5" in stacks_migration_infra/variables.tf for clearer stack identification.

Resource import for migration:

  • Added an import block to stacks_migration_infra/main.tf to import the existing tfe_project.stack_project resource with ID "prj-XzHVjdCZnmdcPEDS", enabling Terraform to manage this resource going forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant