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 Jul 14, 2023. It is now read-only.
While attempting to add a multitenant deployment option, I found that jest test deployments always go to public schema regardless of what is defined in the configOptions.
Adjust the migrations.schema.default schema:
breakpoint after const updateSQL: any = await liquibase(liquibaseOptions).run(updateCmd)
deployments still go to public schema:
The text was updated successfully, but these errors were encountered:
While attempting to add a multitenant deployment option, I found that jest test deployments always go to
public
schema regardless of what is defined in the configOptions.Adjust the
migrations.schema.default
schema:breakpoint after
const updateSQL: any = await liquibase(liquibaseOptions).run(updateCmd)
deployments still go to
public
schema:The text was updated successfully, but these errors were encountered: