-
Notifications
You must be signed in to change notification settings - Fork 1
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
flag provided but not defined: -d #18
Comments
Hey @amirtal-cp, thanks for testing out tgmigrate! The -d flag have been replaced with a Also there is a issue with using the terragrunt hooks #10 that I haven't figured out on how to resolve. As a work around I call tgmigrate separately before running terragrunt when needed. |
hi, i was using the 'plan' command, and running it manually independent of terragrunt plan/apply commands. .tgmigrate.hcl :
V20210518__grafana-test.hcl :
output:
note that there is ~5min delay from the 'Moving ...' notification (shows up instantly when running command), to the 'Uploading ...' line (which actually never completes, i.e. file in s3 is not changed). also tried running migration plan for only a single resource:
with same result. using macOS (catalina 10.15.7), tgmigrate version 0.1.7 is there an option for more verbose output/log ? (possibly fork this as a new issue.) |
Hey, forking this into a new issue would be nice, I have updated the documentation now so then I can close this issue. The issue where it's stuck uploading the state file to the bucket is obviously a bug..
|
on the example given:
there is a reference to a non-existing parameter:
flag provided but not defined: -d
how (if possible) should the plan action be used?
The text was updated successfully, but these errors were encountered: