grafana sourcing AWS credentials for cloudwatch datasource about grafana-boshrelease HOT 4 CLOSED

Either way is broken from a BOSH release perspective. There should be explicit properties added for configuring it so it can be set up in the manifest.

from grafana-boshrelease.

Agreed that AWS cloudwatch credentials should be properties of the bosh job and be optionally set via deployment manifest. I'm happy to send a PR, but thought i'd discuss first.

1 options could be to have grafana_ctl create /home/vcap/.aws/credentials if AWS credentials were provided in deployment manifest, and that the chpst command could be replaced with su -c in order for the grafana-server process to use the vcap users environment variables.

Can you think of a neater way of doing it?

from grafana-boshrelease.

Bleh, that's pretty annoying that you can only configure it with either global state on your OS user or global state on the entire machine. :( I really don't like the idea of a BOSH release modifying the user's home directory. Maybe it could create some other dir and export it as $HOME when running the grafana process?

from grafana-boshrelease.

Let me run some tests with setting $HOME to some arbitrary directory under /var/vcap/ that contains the .aws/credentials file and see if that even works.

I think you can specify additional or overriding environment variables to chpst with the -e switch.

Let me get back to you.

from grafana-boshrelease.