Add ability to set environment variables for daemons #150
Comments
costela
added a commit
to RegioHelden/puppet-prometheus
that referenced
this issue
Jan 24, 2018
costela
added a commit
to RegioHelden/puppet-prometheus
that referenced
this issue
Jan 24, 2018
costela
added a commit
to RegioHelden/puppet-prometheus
that referenced
this issue
Jan 31, 2018
upstart's use of exec means we have to export the variables loaded from the defaults file. Since we're using the same default file for multiple init styles, it seems cleaner to make this exporting explicit on upstart's side. refs voxpupuli#150
costela
added a commit
to RegioHelden/puppet-prometheus
that referenced
this issue
Jan 31, 2018
upstart's use of exec means we have to export the variables loaded from the defaults file. Since we're using the same default file for multiple init styles, it seems cleaner to make this exporting explicit on upstart's side. refs voxpupuli#150
cegeka-jenkins
pushed a commit
to cegeka/puppet-prometheus
that referenced
this issue
Aug 28, 2019
upstart's use of exec means we have to export the variables loaded from the defaults file. Since we're using the same default file for multiple init styles, it seems cleaner to make this exporting explicit on upstart's side. refs voxpupuli#150
Rovanion
pushed a commit
to Rovanion/puppet-prometheus
that referenced
this issue
May 5, 2021
upstart's use of exec means we have to export the variables loaded from the defaults file. Since we're using the same default file for multiple init styles, it seems cleaner to make this exporting explicit on upstart's side. refs voxpupuli#150
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a prerequisite for #149, we probably have to support providing arbitrary environment variables to daemons, similarly to how we use
prometheus::daemon::options.The text was updated successfully, but these errors were encountered: