Open natalieparellano opened 1 year ago
@AidanDelaney should we aim to make use of scafall
? (in addition or instead of?)
I'd love to see scafall
used here.
Let's block this on https://github.com/buildpacks/pack/pull/1534 since whatever we do for buildpacks can be modified for extensions
@natalieparellano I'd like to take a swing at this when unblocked. Assign me this issue, please.
Still blocked on https://github.com/buildpacks/pack/pull/1534
@harikannan512 I apologize for completely missing your comment in https://github.com/buildpacks/pack/pull/1685 - by scafall
we mean https://github.com/buildpacks-community/scafall
@natalieparellano is this issue still up?
I think so - @AidanDelaney do you have any thoughts on this?
@natalieparellano I think it is still up and would love to work on this issue , plz assign me!!
Description
This is a sub-task of https://github.com/buildpacks/pack/issues/1470
Just like scaffold new buildpacks, we should be able to scaffold new extensions
Proposed solution
The command should work just like
pack buildpack new
, but with extensions:Additional context