You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 22, 2023. It is now read-only.
That would be handy, we are trying to initialize a dynamodb running in one container, using an aws-cli container to create a table and once everything is ready, run integration tests in a third container.
This issue has been automatically marked as stale because it has not had any activity in the last 60 days. It will automatically be closed if no further activity occurs in the next seven days to enable maintainers to focus on the most important issues.
If this issue is still affecting you, please comment below within the next seven days.
Thank you for your contributions.
I think it's a pretty common scenario especially for database migration because most db containers do not have the environment(migration tools) to migrate itself. It would be nice to have some kind of short-lived container that do something only for the long-lived container and quit after finished, like k8s Jobs.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Continuation of discussion in #105, for the more advanced use case:
The text was updated successfully, but these errors were encountered: