`kamal app exec -i "bin/rails dbconsole"` requires some password about kamal

[nickhammond]

@dorianmariecom Is your database an accessory? What's the accessory config for this in your deploy.yml?

[dorianmariecom]

Here is my accessory config:

accessories:
  db:
    image: postgres:16.1
    host: 45.55.196.152
    port: 5432
    env:
      clear:
        POSTGRES_USER: code
        POSTGRES_DB: code_production
      secret:
        - POSTGRES_PASSWORD
    directories:
      - data:/var/lib/postgresql/data

[nickhammond]

@dorianmariecom It's prompting for the value you have set for POSTGRES_PASSWORD which would be in your .env file.

[dorianmariecom]

When I enter my database password I get: psql: error: FATAL: password authentication failed for user "code"

Doing psql postgresql://code:[email protected]/code_production works

[dorianmariecom]

When I do kamal app exec -i "echo \$HOST" I get nothing, but if I do kamal app exec -i "printenv" I get all my env variables

[djmb]

I'm not sure there's much we can do to debug this issue here, unless you have some extra information that points to this being a Kamal issue.

You could open a bash shell with kamal app exec -i bash and see if you can work anything more out from in there? I'll close this for now, but if you do find something let us know!

[dorianmariecom]

The environment variables are there with bash but still it asks me for a password even though it's in the DATABASE_URL

~/s/d/code> kamal app exec -i bash
Get most recent version available as an image...
Launching interactive command with version latest via SSH from new container on 164.92.135.114...
root@6655aa5d198f:/rails# echo $HOST
code.dorianmarie.com
root@6655aa5d198f:/rails# bin/rails dbconsole
I, [2024-03-07T04:21:55.633339 #7]  INFO -- : [dotenv] Loaded .env.production
Password for user code: 

[djmb]

You might need rails dbconsole -p:

rails dbconsole -h
Usage:
  bin/rails dbconsole

Options:
  -e,   [--environment=ENVIRONMENT]                    # The environment to run `dbconsole` in (e.g. test / development / production).
  -p,   [--include-password], [--no-include-password]  # Automatically provide the password from database.yml
        [--mode=MODE]                                  # Automatically put the sqlite3 database in the specified mode
                                                       # Possible values: html, list, line, column
        [--header], [--no-header]
  --db, [--database=DATABASE]                          # Specify the database to use.

Start a console for the database specified in config/database.yml

[dorianmariecom]

yeah that works, had no idea about the -p option, probably should be the default