-
Notifications
You must be signed in to change notification settings - Fork 37
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
Dbschema migr -- command side #204
Conversation
|
||
} | ||
|
||
} |
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.
I think there is a use case for users wanting to trigger a rollback manually.
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.
I can agree with that. Let us what @kraftp thinks. In we do that should add a npx db-cloud userdb rollback
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.
Have we decided to separate migrate from deploy and provide a manual migrate command? In that case, yeah, we need manual rollback as well.
npx dbos-cloud userdb migrate
Notes:
dbos-config.yaml needs to be pointing to the right database.
This means you should have run
npx dbos-cloud userdb create ....... to provision the db
npx dbos-cloud applications configure ........... to update dbos-config.yaml