Internally, we're not using buildah source, and I have no way of knowing that anyone else, is, either.

We recently added a --artifact flag to buildah manifest add which generates an artifact manifest for a file and adds that artifact manifest to an image index, but with no functionality for generating an artifact manifest that is not then immediately added to an image index.

Operationally, doing that is not entirely unlike what buildah source does, except that buildah source acts on OCI layouts rather than images (or "images") in local storage, and the result is not an artifact manifest.  This story is about changing how it does things to:

• create an artifact manifest in local storage instead of an image manifest in an OCI layout directory.  The image can be pushed to an "oci:" destination at any point, so we don't need to try to support both methods of storing the content.
• add files to an artifact manifest as artifact "layers" instead of wrapping them in tar headers and footers and then adding them to an image manifest as normal image layers, but with a flag to force the older behavior if it's absolutely necessary for some reason
• drop the custom push subcommand if normal "push" can be made to do the job
• drop the custom pull subcommand if normal "pull" can be made to do the job