Skip to content
This repository has been archived by the owner on May 16, 2022. It is now read-only.

Consume Composer dependency from the dep-server #221

Closed
arjun024 opened this issue Jul 9, 2021 · 0 comments · Fixed by #248
Closed

Consume Composer dependency from the dep-server #221

arjun024 opened this issue Jul 9, 2021 · 0 comments · Fixed by #248
Assignees

Comments

@arjun024
Copy link
Member

arjun024 commented Jul 9, 2021

Per paketo-buildpacks/dep-server#45, we should start consuming the Composer 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.

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants