-
Notifications
You must be signed in to change notification settings - Fork 143
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
Make docker entrypoint 'last_restore_file' runtime-variable #772
Comments
Hi @ericsmalling ! This looks like a great idea and the proposed replacement is neat. Any chance you could find a bit of time to convert this into a PR as well? |
Thanks, I'll tackle this ASAP |
Draft PR #787 open - I could use some pointers on how to add some tests around this though |
Hi. Thanks for the PR. For testing, the first step is to expose the variable via Dockerfile like I did here. The next step would be to pass in a value when the Medusa container actually runs. In Medusa tests, we have the We could also hardcode it at build time, but that feels like a worse solution. Perhaps there's another way to make Medusa's entrypoint see the env var that I can't think of right now. |
Project board link
The hard coded path of for the
last_restore_file
in docker-entrypoint.sh does not work for users that need to use their own path for such files. Recommend using the sameMEDUSA_TMP_DIR
as used in restore.py for consistency.Current:
Proposed replacement:
last_restore_file=${MEDUSA_TMP_DIR:-'/var/lib/cassandra'}/.last-restore
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: MED-5
The text was updated successfully, but these errors were encountered: