Bump DT libbuildpack to Support File-Based VCAP Services#574
Open
wepudt wants to merge 1 commit intocloudfoundry:masterfrom
Open
Bump DT libbuildpack to Support File-Based VCAP Services#574wepudt wants to merge 1 commit intocloudfoundry:masterfrom
wepudt wants to merge 1 commit intocloudfoundry:masterfrom
Conversation
|
|
wepudt
changed the title
wepudt
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumped version of DT libbuildpack to v1.9.0 to introduce support for file-path based VCAP Services to DT.
This allows the use of file-path based VCAP Service feature while injecting apps with DT OneAgent.
I have viewed signed and have submitted the Contributor License Agreement -> Links to the documents are dead and search did not turn up any documents. To my knowledge this is covered by corporate agreement.
I have made this pull request to the
masterbranchI have added an integration test -> no new integration test required.