Teslamate secrets fix

[maindust]

Description

For existing roles;

The issue we were having was that two .ini's were generated and two fact sheets were made. I merged both facts into a singular sheet and created a single .ini to store it. I then added a tag in tasks that allows the user to run sb install sandbox-teslamate-grafana to grab the DB password the user needs when setting up the data source in grafana.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. You can use the checkboxes below or delete them as you wish.

• [ ] I deployed this in my dev box and did not lose any functionality
• [ ] I deployed this to prod once dev validation was done and did not lose any functionality.
• [ ] Validated that teslamate is using new db password that was generated by deleting the DB fact sheet for teslamate_db and only relying on teslamate.ini

[saltydk]

This seems partially handled as you would have to migrate the old postgres password when doing this to avoid causing issues for users who already deployed this, no?

[maindust]

That's fair. What's the preferred method for me to give those who have already deployed the conversion steps? I can make a section in tasks that changes the existing users db pass to the new. Use a trigger of sb install sandbox-teslamate-db-fix or I can put instruction on the docs.

[saltydk]

I can commit a fix tomorrow, sick today so won't rack my brain about the specifics today.

[maindust]

Thanks for the help dude. Hope you get to feeling better soon.

[saltydk]

I've made some tweaks, one of which will require a tweak to the docs I suspect, I believe that users would assume more grafana automation if we used that naming.