Skip to content

Conversation

@semnil
Copy link

@semnil semnil commented Aug 1, 2022

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. 😄

Comment on lines 160 to 163
core.setOutput('terraform_targets', terraformTargetObjs);
if (tfmigrateObjs.length == 0) {
// Running terraform when tfmigrate has nothing to do
core.setOutput('terraform_targets', terraformTargetObjs);
}
Copy link
Author

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.

@suzuki-shunsuke suzuki-shunsuke self-requested a review August 2, 2022 06:33
Copy link
Owner

@suzuki-shunsuke suzuki-shunsuke left a 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).

@semnil semnil requested a review from suzuki-shunsuke August 3, 2022 00:23
@semnil
Copy link
Author

semnil commented Aug 3, 2022

I'm sorry that I misunderstood the content of the issue. 🙇
I have made the change again, does this resolve the issue?

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

Labels

None yet

Projects

No open projects
Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants