-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consume PHP dependency from the dep-server #255
Comments
Should we hold off on this until paketo-buildpacks/dep-server#30 is implemented? |
arjun024
added a commit
that referenced
this issue
Sep 27, 2021
Fixes: #253 Fixes: #255 Also see cloudfoundry/binary-builder#56
5 tasks
arjun024
added a commit
that referenced
this issue
Sep 27, 2021
Fixes: #253 Fixes: #255 Also see cloudfoundry/binary-builder#56
thitch97
pushed a commit
that referenced
this issue
Sep 28, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Per paketo-buildpacks/dep-server#45, we should start consuming the PHP dependency from the dep-server (https://api.deps.paketo.io/v1/dependency?name=<dependency>) instead of the https://buildpacks.cloudfoundry.org/dependencies/<dependency>/... location we currently get the dependencies from.
This will make the dependency publishing/consumption process more transparent than the process we use for the dependencies available via the dependency-builds pipeline.
We have already done this switch-over in the Node Engine and Yarn Buildpacks. The outline of what this work will entail can be found in the dep-server issue linked at the top.
The text was updated successfully, but these errors were encountered: