Not using ssl and sslmode parameters with Heroku / Migrations folder

I’m submitting a…

• Bug report
• Feature request
• Question

Current behavior

When deploying to Heroku, I receive the following error:

[ERROR] AssertionError [ERR_ASSERTION]: ifError got unwanted exception: no pg_hba.conf entry for host "{redacted}", user "{redacted}", database "{redacted}", SSL off
    at module.exports (/app/node_modules/db-migrate/lib/commands/helper/assert.js:9:14)

Procfile:

release: db-migrate up
web: node server.js

Below is my database.json file. The environment in question is “production.”

{
  "development": {
    "driver": "pg",
    "user": {"ENV": "DATABASE_USER"},
    "password": {"ENV": "DATABASE_PASSWORD"},
    "host": {"ENV": "DATABASE_HOST"},
    "database": {"ENV": "DATABASE_NAME"},
    "schema": {"ENV": "DATABASE_SCHEMA"}
  },

  "staging": {
    "driver": "pg",
    "user": {"ENV": "DATABASE_USER"},
    "password": {"ENV": "DATABASE_PASSWORD"},
    "host": {"ENV": "DATABASE_HOST"},
    "database": {"ENV": "DATABASE_NAME"},
    "schema": {"ENV": "DATABASE_SCHEMA"}
  },

  "production": {
    "driver": "pg",
    "url": {"ENV": "HEROKU_POSTGRESQL_BLACK_URL"},
    "ssl": true,
    "sslmode": "require"
  }
}

I hard-coded the ssl and sslmode values after first trying them as environment variables.

I checked and the proper database name and user are being read from the URL.

Expected behavior

db-migrate attempts to connect using ssl.

Environment

db-migrate version: 0.11.6
db-migrate driver with versions: db-migrate-pg 1.0.0

Additional information:
- Node version: 12.3.1
- Platform:  Windows 10

[paulmiller3000]

@desmondmc Glad I could help!

[jasper-lyons]

* As @paulmiller3000 pointed out db-migrate kept using my `dev` config for some reason, even though i was passing `-e prod` to the db-migrate command (`heroku run db-migrate up --config database.json -e prod --app my-app`). It kept saying something about "prod not valid avoid using ';'"

Just solved this issue myself. FYI, the heroku command will eat your -e param so db-migrate never receives is. If you instead do heroku run bash and then run your commands from the bash cli, it should work (I had success with this).