Kristaps Fabians Geikins
37d51072fb
* WIP new mutation arg * limited resource token creation done * token resource rule creation validation * updated authorizeResolver implementation * introduced resource access rule checks in authorizeResolver everywhere * more checks added * updated projects resolvers * updated stream resolvers * more checks added * error page theme resolution fix * WIP testss * more tests * implemented checks in REST auth pipeline * REST API coverage & tests * some tests fixed * test fixess * added tests * feat(server): new automation result reporting scope (#1976) * feat(server): new automation result reporting scope * tests fix
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.