Using ps:exec overwrites config

[nixme]

Because the buildpack installs extra.sh into /app/.profile.d/datadog.sh if you SSH into a running dyno with heroku ps:exec that script will execute on login, modifying the (running) agent's conf.yml and integrations.

This is especially an issue because the environment for ps:exec doesn't set all the heroku config vars. So the script overwrites the agent configuration with basically a not-configured conf file.

[nixme]

I think a better approach would be similar to bin/start-nginx in the https://github.com/heroku/heroku-buildpack-nginx

Then user's of the buildpack would opt-in via the Procfile: web: bin/start-datadog bundle exec bin/puma

[arapulido]

@nixme Thanks for the suggestion! We will see how we could improve this

[jeffblake]

I am also running into this issue, trying to SSH into a dyno to check integrations that only run in the web dyno, not a one-off run process.