Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alerta does not pick up on non-default Postgres credentials #444

Open
davidusken opened this issue Dec 15, 2023 · 0 comments
Open

Alerta does not pick up on non-default Postgres credentials #444

davidusken opened this issue Dec 15, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@davidusken
Copy link

Issue Summary
When using credentials other then the default ones for Postgres, Alerta does not use them.
This results in having the password in cleartext in Git when wanting to use non-default credentials.

Environment

  • OS: Linux

  • API version: 9.0.1

  • Deployment: Docker

  • Database: [eg. MongoDB, Postgres]

  • Server config:
    Auth enabled? Yes
    Auth provider? OpenID
    Customer views? No
    (or provide the /config endpoint output)

  • web UI version: 9.0.1

  • CLI version: 9.0.1

To Reproduce
Steps to reproduce the behavior:

  1. Update alerta-postgresql with different credentials
  2. Re-deploy app
  3. Verify auth fails for alerta user as credentials alerta:PG_ALERTA_PASSWORD no longer works

For web app issues, include any web browser JavaScript console errors.

Expected behavior
Best case scenario the database URL should read from the secret.
Alternatively it should work to supply the new password as an env variable and use this syntax:
DATABASE_URL = "postgresql://alerta:${PG_ALERTA_PASSWORD}@fmonitoring-alerta-postgresql:5432/alerta"
(Tested this and it does not use the env variable to authenticate)

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

NOTE: Please provide as much information about your issue as possible.
Failure to provide basic details about your specific environment make
it impossible to know if an issue has already been fixed, can delay a
response and may result in your issue being closed without a resolution.

@satterly satterly added the bug Something isn't working label Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants