db-migrate / db-migrate/node-db-migrate
No valid versions available for db-migrate-redshift/No such driver found, please try to install it via npm install db-migrate-redshift or npm install -g db-migrate-redshift
- Dominant language
- JavaScript
- Stars
- 2.3k
- Forks
- 361
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] Bug report
## Current behavior
1. I was using db-migrate-redshift and created up & down files for redshift migration.
When I re-create the docker image again, **npm install -g db-migrate-redshift** installation is failed.
2. So, updated docker file with **npm install -g db-migrate-awsredshift** ( successfully installed ) and able to create up and down files.
## Expected behavior
1. Successful Installation with "db-migrate-redshift" and migration should work for the up & down files created.
2. migration should work for the up & down files created.
## Environment
Image has been created using Docker file :
```
FROM ubuntu:18.04
RUN apt-get update -yqq
RUN apt-get install -yq default-jre
RUN apt-get install -yq openjdk-8-jre-headless
RUN apt-get install -yq bash
RUN apt-get install -yq curl
RUN apt-get install -y nodejs
RUN apt-get install -y npm
# # Install db-migrate
RUN npm install -g db-migrate
RUN npm install -g db-migrate-awsredshift
```
Versions :
db-migrate --version : 0.11.13
npm --version : 6.14.12
node version : v10.24.1
db-migrate-awsredshift : 0.1.1
logs :
1.
```
npm ERR! code ENOVERSIONS
npm ERR! No valid versions available for db-migrate-redshift
npm ERR! A complete log of this run can be found in:
npm ERR! /home/ec2-user/.npm/_logs/2022-03-21T03_13_22_722Z-debug.log
```
2( after installing db-migrate-awsredshift ) .
`Migration command : db-migrate up --migration-table
[ERROR] AssertionError [ERR_ASSERTION]: ifError got unwanted exception: No such driver found, please try to install it via npm install db-migrate-redshift or npm install -g db-migrate-redshift
at module.exports (/home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/lib/commands/helper/assert.js:9:14)
at /home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/lib/commands/up.js:19:14
at /home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/connect.js:17:7
at Object.exports.connect (/home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/lib/driver/index.js:76:16)
at Object.exports.connect (/home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/lib/driver/index.js:77:11)
at Object.exports.connect (/home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/connect.js:15:10)
at /home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/lib/commands/up.js:15:13
at tryCatcher (/home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/node_modules/bluebird/js/release/promise.js:547:31)
at Promise._settlePromise (/home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromiseCtx (/home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/node_modules/bluebird/js/release/promise.js:641:10)
at _drainQueueStep (/home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/node_modules/bluebird/js/release/async.js:97:12)
at _drainQueue (/home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/node_modules/bluebird/js/release/async.js:86:9)
at Async._drainQueues (/home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/node_modules/bluebird/js/release/async.js:102:5)
at Immediate.Async.drainQueues [as _onImmediate] (/home/ec2-user/.nvm/versions/node/v10.24.1/lib/node_modules/db-migrate/node_modules/bluebird/js/release/async.js:15:14)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)`
Appreciate your comments & suggestions on the above issue. Thank you.
Contributor guide
Assessment
This issue has not been assessed yet.