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

User defined Grafana username and password not imported from Ansible #932

Closed
AstroProfundis opened this issue Nov 24, 2020 · 0 comments · Fixed by #937
Closed

User defined Grafana username and password not imported from Ansible #932

AstroProfundis opened this issue Nov 24, 2020 · 0 comments · Fixed by #937
Assignees
Labels
category/monitoring Categorizes issue or PR related to monitoring components. priority/P2 Indicates that the priority of a issue is higher than normal issue. status/TODO Categorizes issue as we will do it. type/bug Categorizes issue as related to a bug.
Milestone

Comments

@AstroProfundis
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
    If the user set custom Grafana username and password in Ansible inventory file, and have not changed it after deployment, those settings are ignored during import and the imported Grafana falls back to default admin / admin credentials.
    图片

  2. What did you expect to see?
    The configs are kept and correctly set after import.

@AstroProfundis AstroProfundis added type/bug Categorizes issue as related to a bug. status/TODO Categorizes issue as we will do it. priority/P2 Indicates that the priority of a issue is higher than normal issue. labels Nov 24, 2020
@AstroProfundis AstroProfundis added this to the v1.2.5 milestone Nov 24, 2020
@AstroProfundis AstroProfundis self-assigned this Nov 24, 2020
@lucklove lucklove modified the milestones: v1.2.5, v1.2.6 Nov 30, 2020
@lucklove lucklove modified the milestones: v1.2.6, v1.3.0 Dec 15, 2020
@AstroProfundis AstroProfundis added the category/monitoring Categorizes issue or PR related to monitoring components. label Dec 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category/monitoring Categorizes issue or PR related to monitoring components. priority/P2 Indicates that the priority of a issue is higher than normal issue. status/TODO Categorizes issue as we will do it. type/bug Categorizes issue as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants