Skip to content
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

Option to run only one execution when using TG hooks with -all option #10

Open
aleksanderaleksic opened this issue Jan 26, 2021 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@aleksanderaleksic
Copy link
Owner

aleksanderaleksic commented Jan 26, 2021

When running terragrunt apply-all /plan-all multiple executions of tgmigrate meaning there is a migrationcheck for one module at the same time. This will cause race condition.

Suggestion is to add a flag like --max-concurrent-executions 1 where if it is applied the executions above execution nr.1 would be skipped. This "state" would be stored localy in a file, but it must be known where the file is located.

@aleksanderaleksic aleksanderaleksic added the enhancement New feature or request label Jan 26, 2021
@aleksanderaleksic aleksanderaleksic self-assigned this Jan 26, 2021
@aleksanderaleksic
Copy link
Owner Author

After trying to fix this I think its best to implement a "before_all" hook on the terragrunt repo. I will try to make a PR for that shortly, in the meantime you should run tgmigrate manually before the apply.

@aleksanderaleksic
Copy link
Owner Author

Haven't had time to look into the before-all hook on the terragrunt repo but I will try to get time for that later

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant