pushhave the following behaviors:
buildcalculates a tophash based on the package entry data, package entry metadata, and top-level package metadata, injects that into the package manifest, and stores the package manifest in the local registry.
pushuploads the entries in the package to a remote registry, performs the same tophash calculations, and stores a package manifest referencing the remote files in the remote registry.
pushtargets a remote registry;
buildtargets a local registry
pushcopies package files;
buildleaves files where they are
pushcreates materialized packages: packages which point solely to files located in an S3 bucket.
registry. For example: