Contrast security hook - #192
Conversation
|
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/166244543 The labels on this github issue will be updated when the story is started. |
|
❌ Hey gmoore! All pull request submitters and commit authors must have a Contributor License Agreement (CLA). Click here for details on the CLA process. The following github user @gmoore is not covered by a CLA. After the CLA process is complete, this pull request will need to be closed & reopened. DreddBot will then validate the CLA(s). |
|
We have a CLA in place and my Github use is in the correct organization with the correct publicity permissions. Please see our contribution tot he java buildpack here: cloudfoundry/java-buildpack#446 |
Or not... Resubmitting now. |
Contrast Security provides agents that our customers can inject into their code in order to both discover vulnerabilities and block attacks. This change makes it easier for NodeJS applications to integrate with Contrast Security.
Contrast Security already integrates with Cloud Foundry through our code in the Java Buildpack as well as our tile available to PCF and Bluemix users. The use case that this change solves is that an operations engineer can configure Contrast Security credentials for an entire org or space, and applications pushed to that space can consume those credentials without any extra configuration on their part. Without this integration, application developers must manage different credentials for different environments themselves.
I have viewed signed and have submitted the Contributor License Agreement
I have made this pull request to the
developbranchI have added an integration test