-
Notifications
You must be signed in to change notification settings - Fork 288
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
pack should support pack extension *
commands
#1470
Comments
What is the purpose of this command ? Can you elaborate please ? @natalieparellano |
Ah - this is to provide similar functionality to what you get with |
Blocking on buildpacks/rfcs#173 getting approved and merged. |
Hi @natalieparellano I'm new to this repo. Can you please guide me to appropriate code part? and a bit of explanation about the issue would be really helpful! |
@oovk it would be awesome to get your help on this! At a high level, this is about creating a From a How does that sound? Let us know if you'd like this issue assigned to you! |
pack extension package
pack extension *
commands
@natalieparellano can you please assign me issue #1470 or #1489 or similar to pack extension, i'm guessing they would be a good first issue for me |
@natalieparellano can you please open up an issue for the implementation of inspect command, I'll now try my hands to implement it |
Reopening as we now have
(We can skip the registry stuff for now - that requires further thought) |
pack extension --help
should show (analogously topack buildpack --help
):We should probably make a separate issue for each one of these commands, as they could be implemented separately.
Edit: Made a separate issue (#1489) for
pack extension package
.The text was updated successfully, but these errors were encountered: