Editing someone else's bundle

[carolynvs]

People have asked how to edit and fork a published bundle, or just get a deeper look into what is in the bundle. Right now we recommend using the bundle's original source code, changing it as appropriate and then publishing it to your own repository. That doesn't always work though for bundles that don't distribute their source.

I'd like to extend what information is available in porter inspect so that you can also see:

• Additional bundle metadata such as the maintainer, keywords, custom data, etc. For example, when we add labels to bundles, they would be displayed as well. Essentially we should give you a human friendly way to get the bundle.json back out of a published bundle.
• An output flag so that you can just see the bundle.json, e.g. porter inspect --output json returns the bundle.json (without the canonical formatting which is impossible to read). The output of inspect is already a human readable view of the bundle.json so having a different output format that just gives you the file seems a natural extension.

A new command that extracts the bundle's filesystem to a directory would also be pretty useful for the purpose of extracting a particular file from a bundle, or editing the bundle so it can be republished elsewhere.

porter unpack getporter/porter-hello:v0.1.1 --destination DIRECTORY
# Extract all files in /cnab to DIRECTORY

Someone could then fork/edit a bundle would look like this:

mkdir myfork && cd myfork
porter unpack getporter/porter-hello:v0.1.1
# edit the bundle's files in the current directory
porter publish --registry ghcr.io/myfork