-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add terraform execution condition #436
base: main
Are you sure you want to change the base?
Add terraform execution condition #436
Conversation
core.setOutput('terraform_targets', terraformTargetObjs); | ||
if (tfmigrateObjs.length == 0) { | ||
// Running terraform when tfmigrate has nothing to do | ||
core.setOutput('terraform_targets', terraformTargetObjs); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The differences other than these changes are the result of running npm run build
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your contribution.
I think this change has a problem.
tfaction supports Monorepo, and doesn't restrict the use case that Terraform and tfmigrate are run in multiple working directories.
This change restricts those use cases and includes a breaking change.
#386 intends to prevent both terraform and tfmigrate from being run in the same working directory (I fixed the issue title).
I'm sorry that I misunderstood the content of the issue. 🙇 |
I had an incident where I forgot to add a skip label and the resource was deleted. 😢
I don't think it is necessary to run terraform as long as the goal is to run tfmigrate.
Also, I believe the following issues can be resolved.
ref: #386
Please let me know if additional action is needed and I will respond. 😄