-
Notifications
You must be signed in to change notification settings - Fork 172
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
Tracking Issue: Buildpack Dependency Repo Migration #926
Comments
We're part-way through migrating the buildpack infrastructure. New dependencies are being put in the new bucket. The bucket is used for other aspects of the buildpacks CI pipeline and we are working on updating those other usages currently. The main (known) outstanding piece of work is to update the bosh releases to point to that bucket for their final releases |
@robdimsdale @dsboulder Is there any remaining work for this? Are we good to close this out? |
This was successfully moved! Though it's backed by Steve G's cloudflare and not a CFF-owned cloudflare. Chris Clark and Steve are going to eventually move that distribution as well. |
@christopherclark Do you want to keep this issue open to track the cloudflare migration work? |
Can we get an estimated date for when this shift might happen? I want to be prepared for that timestamp/date. Thanks! |
There is no concrete date yet but when we have a plan for the migration we will update here. |
Work has started on the CloudFlare migration. |
@Gerg any updates on this? |
ping @Gerg ^ |
Summary
We are in the process of migrating the buildpacks dependency repository (
buildpacks.cloudfoundry.org/dependencies/*
) from an externally-managed Amazon S3 bucket to one controlled by the Application Runtime Interfaces Working Group. This is a tracking issue to help communicate progress.Steps
The text was updated successfully, but these errors were encountered: