Running "mikro-orm migration:check" without a database connection

[ryanisaacg]

Hi, I'm trying to run a check in CI to see if there are any migrations that need to be generated before some code is merged. However, in my CI environment I don't have access to a postgres instance, and I get this issue when running yarn mikro-orm migration:check

mikro-orm migration:check

Check if migrations are needed. Useful for bash scripts.

Options:
  -v, --version  Show version number                                   [boolean]
  -h, --help     Show help                                             [boolean]

Error: No database specified, please fill in `dbName` or `clientUrl` option

Is there any way to set up a config without a connection to a database, and check if migration files are up-to-date?

[B4nan]

Do you have a snapshot file generated (and committed)? It should be preferred over the actual schema inference.

[ryanisaacg]

This is what my config looks like, if it helps:

import { Options, defineConfig } from "@mikro-orm/postgresql";
const CI_DATABASE_CONFIG: Options = defineConfig({
  metadataProvider: TsMorphMetadataProvider,
  entities: ["./lib/entities"],
  migrations: {
    emit: "ts",
    pathTs: "src/migrations",
    path: "lib/migrations",
  },
});

[ryanisaacg]

@B4nan is there any change I need to make to my config to use the snapshot file when the database isn't available?

[ryanisaacg]

Turns out I needed to add connect: false and specify the snapshot DB name in migrations

[petergledhillinclusive]

We have the same problem since v6. The connect: false makes the check command work without trying to connect to a db but it does mean we have to have a different config for this command.

[B4nan]

This should help: ef5d14a

Nowadays it's actually fine to just disable the eagerly created connection since there are fallbacks that will create one if it's not there yet lazily.