Gergő Jedlicska
f210d9b749
* feat(projects): add project regions, default to null * feat(multiregion): add projectRegion Db client lookup logic * feat(multiregion): add project region repositories and caching * feat(multiRegion): db initialization and get project db client * feat(docker-compose): add second db for regions testing * feat(multiRegion): initialize region with pubs and subs working * fix(multiRegion): get region client even if it was registered in another pod * feat(workspaces): create workspace resolver split * feat: update server region metadata * feat(projects): rewrite project creation * feat(multiRegion): getRegionDb * fix(workspaces): get projects now can retur null * feat(multiRegion): make local multi region DB-s work * feat: set d efault workspace region * CR changes * tests * feat(multiRegion): bind region properly * fe update * test fixes * feat(multiRegion): automatically create aiven extras plugin * ci(postgres): use published postgres with aiven extras * fix(multiRegion): roll back the aiven extras migration, there is a better way * tests fix * fix(billing): we do not need to add a seat, if the workspace is on a plan, but has no sub --------- Co-authored-by: Kristaps Fabians Geikins <fabis94@live.com>
Migrations, and how to create them
First, make a new migration file in the appropriate migrations folder. To do this use ./bin/cli.
Next, write your migration! Here's an example below that adds a new column to a table.
/* istanbul ignore file */
exports.up = async (knex) => {
await knex.schema.alterTable('scopes', (table) => {
table.boolean('public').defaultTo(true)
})
}
exports.down = async (knex) => {
let hasColumn = await knex.schema.hasColumn('scopes', 'public')
if (hasColumn) {
await knex.schema.alterTable('scopes', (table) => {
table.dropColumn('public')
})
}
}
Notes:
- Do not delete or edit existing migration files
- To edit an existing table, use alter table in a new migration file.
- Always prefix your migration file with the date that you authored it in.