-
Notifications
You must be signed in to change notification settings - Fork 319
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
Improve down.sh script #2778
Improve down.sh script #2778
Conversation
Signed-off-by: Martynov Maxim <martinov_m_s_@mail.ru>
Thanks for opening your first pull request in the Marquez project! Please check out our contributing guidelines (https://github.com/MarquezProject/marquez/blob/main/CONTRIBUTING.md). |
✅ Deploy Preview for peppy-sprite-186812 canceled.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2778 +/- ##
=========================================
Coverage 84.47% 84.47%
Complexity 1429 1429
=========================================
Files 251 251
Lines 6460 6460
Branches 299 299
=========================================
Hits 5457 5457
Misses 850 850
Partials 153 153 ☔ View full report in Codecov by Sentry. |
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 @dolfinus for the usage updates 💯 💯 🥇
Great job! Congrats on your first merged pull request in the Marquez project! |
Problem
👋 Thanks for opening a pull request! Please include a brief summary of the problem your change is trying to solve, or bug fix. If your change fixes a bug or you'd like to provide context on why you're making the change, please link the issue as follows:
./down.sh
script is failing with error message:This is because
docker-compose.yml
contains environment variables substitution, and these variables are not set, unlikeup.sh
. The issue was introduced in #2678.After filling up these variables I've got another error:
This is because volumes are removed using
docker volume rm & docker volume rm
chain, and if some volume is already removed, command will exit with error, and other volumes will not be deleted.Solution
Please describe your change as it relates to the problem, or bug fix, as well as any dependencies. If your change requires a database schema migration, please describe the schema modification(s) and whether it's a backwards-incompatible or backwards-compatible change.
down.sh
scriptdocker-compose down -v
flag which should do this automaticallydowh.sh
without arguments now left volumes intact, users have to passdowh.sh -v
flag to remove them.One-line summary:
Fixed down.sh script error, added new -v option.
Checklist
CHANGELOG.md
(Depending on the change, this may not be necessary)..sql
database schema migration according to Flyway's naming convention (if relevant)