Skip to content

Bug passing parameters to umzug #679

Description

@ricardopolo

What are you doing?

Configuring sequelize client for migrations, using a .sequelizerc file that looks like this:

const path = require('path');

module.exports = {
  'config': path.resolve('migrations/config'),
  'migrations-path': path.resolve('migrations'),
  'seeders-path': path.resolve('migrations/seeders'),
  'models-path': path.resolve('migrations/models')
};

What do you expect to happen?

This should work without alerts.

What is actually happening?

It's throwing warnings
image 2018-07-30 at 11 43 25 am
Related to this line in umzug https://github.com/sequelize/umzug/blob/3f7c126bedd81e5572721e00282644112cc2d2a7/src/index.js#L471

Looks like you are not passing config.js and model.js to umzug, but just passing config and models, which does not match the expected pattern.

Dialect: postgres
Sequelize version: v4.38.0
Tested with latest release: Yes

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions