-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Cloud Native Buildpack integration #314
Comments
@dwillist sounds like fun! I've been pondering ways to make dive more naturally extensible but haven't started that undertaking yet. It would be helpful to learn more about your specific use cases and potential changes they would bring: would this mean adding extra columns to tabular output? modifying existing row data? adding more UI panes? Would this affect the file-tree layout as well? I'm curious to hear more about what you had in mind. |
@wagoodman, Hey apologies for the delay. We are looking to make a couple changes namely:
here is a sample mock up of what we are looking to accomplish: Would love to give you a bit more of an idea how our project works, how we use dive & how we could expose our metadata to the UX. Would you be available to zoom some time this week? |
@dwillist no problem. I'd be down for a zoom chat, feel free to reach out on linkedin or a twitter DM |
Hey,
Thanks for the great tool!
I’m wondering how interested you’d be in collaborating with the Cloud Native Buildpacks (CNB) project? The TLDR; of the CNB project is provide tools to build OCI images without Dockerfiles. Because we build images in a different way, they have lot of additional metadata.
Can you give us a way to render this extra-metadata to make these images more valuable? It seems most of the
dive
rendering logic is couple to the underlying data structures, and we would like an effective way to change some of the contents of theLayers
,LayerDetails
andImage Details
displays.@nebhale
The text was updated successfully, but these errors were encountered: