Buildpack Registry

[jromero]

Based on RFCs:

• https://github.com/buildpacks/rfcs/pull/35
• https://github.com/buildpacks/rfcs/pull/66
• https://github.com/buildpacks/rfcs/pull/75

Tasks:

• [x] GHA buildpack registry automation
• [x] Buildpack Registry config commands
• [x] Update pack build -R to use named buildpack registries
• [x] Default official registry
• [ ] Headless support for buildpack registration
• [ ] Aggregate publish buildpack command

[dfreilich]

Do we link the other issues to this one?

[jromero]

We had ZenHub managing epics. Since we stopped using it, I will add the issues to the description.

[jkutner]

@jromero most of the tasks listed here were called out as "Future Work" in the RFC. Are they a blocker for shipping the first MVP of Buildpack Registry?

[jromero]

@jkutner

What do we mean by MVP?

I think only 2 tasks listed are future work, https://github.com/buildpacks/pack/issues/748 and https://github.com/buildpacks/pack/issues/749. The others probably need to get done to get a nice consistent UX.

EDIT: To elaborate a bit more, the config commands are in future work but we have some commands already built out as per @elbandito. That's what I meant by consistent.

[jromero]

Further conversations on "MVP" occurred on: https://buildpacks.slack.com/archives/C01BMB6DXR8/p1601400706004100

You may join our slack via: https://slack.buildpacks.io