-
Notifications
You must be signed in to change notification settings - Fork 105
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
Grafana 5.0.3 Users passwords being set and datasources created on every puppet run #104
Comments
I can't confirm the bug with the datasources, but I can confirm that behavior for users. Given that the API doesn't support to "get" the password for a user and the fact that providers in puppet need to know the value to compare it, I think there is no "proper" solution to fix this problem. A possible option would be to set passwords only for new users and ignore the password attribute when updating existing users. This would require to sacrifice the ability to change passwords via puppet, but maybe that's the better option instead of changing it on every puppet run and therefore issuing useless API requests. |
A simple solution to check a password is using it, e.g. an api call to log in. I have used this kind of behaviour a couple of times. With a successful login, you can validate if the password is set correctly. |
This reverts commit 3d73de8.
This commit fixes the issue that on each puppet run the user password will be set. As the grafana API does not provide any feature for that we try to connect as that user if login works we suppress the password change. Fixes voxpupuli#104
This commit fixes the issue that on each puppet run the user password will be set. As the grafana API does not provide any feature for that we try to connect as that user if login works we suppress the password change. Fixes voxpupuli#104
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Create a datasource or user by any supported method.
What are you seeing
On every puppet agent run, every datasource is re-created and passwords for users are being re-set (instance method is returning an empty string).
What behaviour did you expect instead
Datasources are created once if they don't already exist. Users are created and hashes checked??
Output log
Any additional information you'd like to impart
The text was updated successfully, but these errors were encountered: