Closed TuckerWhitehouse closed 8 years ago
We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/114424769.
Hey @TuckerWhitehouse we like the idea of giving users the ability to deploy an app and have it "automagically" connect to the newrelic service, however aren't keen on the idea that the binary exists in the buildpack. Here's an outline of some challenges:
In order to support a 3rd party vendor with a redistribution license that is incompatible with Cloud Foundry’s needs: A legal process would need to take place to remedy the licensing incompatibility. In the case where a vendor refuses to modify their licensing:
We're currently researching a solution that would still enable the user the magic the java buildpack provides, but without having the binary in the buildpack.
I'm sorry, but haven't these issues already been resolved in respect to the java buildpack, or is the licensing and security somehow different when it applies to node?
Hey @TuckerWhitehouse we've discussed this issue and are considering this request
Any news to share on this?
@aloismayr thanks for reaching out, no news as of yet.
We would be open to receiving a pull request from the team at New Relic or from the community. At this point we do not have any plans on performing this line of work ourselves.
Would be beneficial to have newrelic bundled similar to the java buildpack, with configuration driven through environment variables.