Build contents diff RFC

[sampeinado]

Readable

[matthewmcnew]

My big existential question on this RFC is if this functionality makes sense as part the kp cli. Up to this point all the functionality in kp has been about interacting with kpack via the kubernetes api. However, this functionality would involve reading and parsing cnb image metadata outside of kpack interaction.

That might be more generally useful as part as another standalone tool or via pack. This diffing is probably useful to the broader cnb ecosystem as well.

[mgibson1121]

I'd advocate for its inclusion in the kp CLI. A common complaint about the developer experience of using kpack is the need to use other tools in conjunction with kp. Given that this workflow would be very helpful to developers when debugging problems, it makes sense to provide this to them as an available tool without having to look elsewhere.

[tylerphelan]

I think we should include this functionality in kp (working with any CNB-created image tag) regardless of if pack includes it because I don't think it would hurt kps usability by having this feature.

I also think we should have a -o json/yaml flag for this for programatic uses of this feature.

[jromero]

What's the status of this RFC? I can see the value of this feature and would throw my +1 on making it a kp feature in that, with my current understanding, it would leverage build information available via kpack (k8s) and not just solely what is available on the images. For example, config/resource changes and build times aren't things that are on the image as far as I'm aware.

[tomkennedy513]

Closing due to staleness and that this seems better in the kpack cli repo