Skip to content
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 MRI dependency from the dep-server #269

Closed
sophiewigmore opened this issue Jul 7, 2021 · 0 comments · Fixed by #296
Closed

Consume MRI dependency from the dep-server #269

sophiewigmore opened this issue Jul 7, 2021 · 0 comments · Fixed by #296
Labels
enhancement A new feature or request
Projects

Comments

@sophiewigmore
Copy link
Member

sophiewigmore commented Jul 7, 2021

Per paketo-buildpacks/dep-server#45, we should start consuming the MRI dependency from the dep-server (https://api.deps.paketo.io/v1/dependency?name=ruby) instead of the https://buildpacks.cloudfoundry.org/dependencies/ruby/... 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.

@sophiewigmore sophiewigmore added the enhancement A new feature or request label Jul 7, 2021
@sophiewigmore sophiewigmore added this to Inbox in Ruby via automation Jul 7, 2021
Ruby automation moved this from Inbox to Done Sep 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement A new feature or request
Projects
Ruby
Done
Development

Successfully merging a pull request may close this issue.

1 participant