Error connecting in database manager

Wappler General Bugs
13

Oh good catch @George . The production target db.json didn't have the connection block at all. Only;

{
  "schema": {}
}

So I manually added the connection block

{
  "type": "postgres",
  "connection": {
    "host": "HOSTNAME",
    "port": 5432,
    "user": "USERNAME",
    "password": "PASSWORD",
    "database": "DATABASE",
    "ssl": {
      "rejectUnauthorized": false
    }
  },
  "schema": {},
  "direct": true
}

Restarted Wappler and the connection worked, button is no longer greyed out and Wappler went ahead and automatically added the below to the db.json and I'm now able to apply changes to the production target.

"schema": {
    "schemas": [
      "public",
      "_heroku"
    ],
    "tables": {},
    "views": {
      "pg_stat_statements_info": {
        "db": {
          "schema": "public"
        }
      },
      "pg_stat_statements": {
        "db": {
          "schema": "public"
        }
      }
    }

So out of curiosity, I fired up a brand new application using the wappler + heroku workflow outlined in the repro steps above. And again I was met with the "blank" Production target db.json. Is it perhaps an issue where it fails to generate the db.json properly in this particular workflow?

Also, you're amazing! thank you for catching that so quickly. :clinking_beer_mugs: