Closed pavankrish123 closed 5 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/162818689
The labels on this github issue will be updated when the story is started.
Duplicate of issue#27
What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running
cf curl /v2/info && cf version
)?"name": "PCF Small Footprint", "build": "2.3.0-build.264", "support": "https://support.pivotal.io"
What version of the buildpack you are using? cf version 6.40.0+07673feb9.2018-10-08
If you were attempting to accomplish a task, what was it you were attempting to do?
We are planning to add support for instrumenting PCF .NET Core Windows applications using AppDynamics using an extension buildpack. We have achieved the same for applications deployed using dotnet_core_buildpack and hwc_buildpack.
We just have to be able to copy some bits in the supply phase of our extension buildpack and set some environment variables in the finalize phase via profile.d scripts.
What did you expect to happen?
I would expect binary_buildpack to use the supply buildpacks changes.
What was the actual behavior?
Since multi buildpacks are not supported, I am getting a warning
Warning: the last buildpack is not compatible with multi-buildpack apps and cannot make use of any dependencies supplied by the buildpacks specified before it
Just wondering when the support will be added for tackling multi buildpacks.
Please confirm where necessary: