-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 -f option to drop command #390
Add -f option to drop command #390
Conversation
Pull Request Test Coverage Report for Build 767
💛 - Coveralls |
Pull Request Test Coverage Report for Build 765
💛 - Coveralls |
internal/cli/main.go
Outdated
} else { | ||
log.fatal("Aborted dropping the entire database schema") | ||
dropFlagSet := flag.NewFlagSet("drop", flag.ExitOnError) | ||
responseYes := dropFlagSet.Bool("y", false, "Drop the entire database schema") |
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.
Not sure about using -y
. Most other CLIs use -f
for this behavior.
The flag help text should be more descriptive.
If we use -f
, something like Force the drop command by bypassing the confirmation prompt
might work.
Any ideas for a short descriptive help text?
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.
Thanks for your confirmation!
You are certainly right.
I'm sure the help text you wrote is fine too.
I’ve added commits for fix. Could you check it? 🙏
Hi,
This #360 change caused that the y/n prompt will appears when dropping the database, it has made inoperable our database drop job of kubernetes.
I think that the drop command should have
-y
option for CI/CD operations (Of course, we can also use the yes command, but it is so painful).