Skip to content

Change db:create or create a command db:createifnotexists or similar. #783

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

Closed
rohit-joy opened this issue Mar 19, 2025 · 5 comments
Closed
Assignees

Comments

@rohit-joy
Copy link

rohit-joy commented Mar 19, 2025

Related to dockerfile: during initialization of a Kubernetes cluster, we need to db:create, then db:migrate. But we don't know whether the db already exists. So please change or add a new command like db:createifnotexists.

@rohit-joy rohit-joy changed the title Change db:create to db:createifnotexists or similar. Change db:create or create a command db:createifnotexists or similar. Mar 19, 2025
@excelsior
Copy link
Collaborator

excelsior commented May 21, 2025

@rohit-joy The task is ready, will be deployed alongside Keycloak support. Let me know if you need it sooner.

@jeannekitchens
Copy link

@rohit-joy this is to be deployed alongside Keycloak support. What is needed here to verify this ahead of the KeyCloak request?

@rohit-joy
Copy link
Author

@excelsior Is this Issue attached to a PR? Basically, we just need to verify with the swagger endpoint exists and can call it with Auth token or KeyCloak token.

@excelsior
Copy link
Collaborator

Merged and pushed in the CLLC repo.

The new task is called db:create_if_not_exists

@edgarf
Copy link
Collaborator

edgarf commented May 27, 2025

@rohit-joy - can we close this task?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants