-
Notifications
You must be signed in to change notification settings - Fork 294
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 inspect
when image built with extensions should show the extensions
#1486
Comments
hey @natalieparellano, i am interested to contribute in this issue could you plz drop some insight as i am new to open source and this will be my first project |
@jalajk24 it would be awesome to get your help here! At a high level, when inspecting the image, pack:
I think the changes required here would largely involve copying what we have for buildpacks and updating it so that it's valid for extensions. It's worth noting - this open PR for platform 0.10 support introduces some changes to the way inspect image is working (updating the lifecycle library code that is imported) and you probably want those changes to land before introducing others. I'm actively working to fix up the open PR today and hopefully it will be merged soon. If you wanted to branch off Thanks again for your help and please don't hesitate to reach out with any further questions! |
hey , can I contribute to this issue ? |
tell me the setup , as I could not find that |
@jalajk24 were you still interested in taking this up? Please let us know... otherwise @Abhi149209 you are welcome to claim it - https://github.com/buildpacks/pack/blob/main/DEVELOPMENT.md will have useful information for configuring your setup. |
@natalieparellano yes i am interested in this plz assign it to me. |
This output should include
Extensions
if extensions were used:The text was updated successfully, but these errors were encountered: