Should we distribute dependencies with the bundle?

[carolynvs]

Let's say that we have a bundle that depends upon another bundle, and its dependency section contains an exact full reference, e.g. getporter/mysql:v1.2.3. When the root bundle is relocated across an airgap, the referenced dependency is no longer accessible. Even if the dependency is relocated manually, how would the root bundle resolve the dependency to the new location?

When porter archives a bundle, it should archive the dependencies into the same archive file. When the archive is published, porter should publish each dependency, and then publish the root bundle with a relocation-mapping.json file that includes the mapping for each dependency.

bundlename-version.tgz
- layers
- manifest.json
- dependencies/
  - bundlename-version/ ...
    - layers
    - manifest.json

It should be an option to only archive the root bundle or archive all dependencies (not sure which should be the default). This will allow an administrator to do a simplified transfer of a bundle and all its dependencies, or when transferring lots of bundles, do each one separately to avoid redundantly large bundles.

We could potentially support archiving all dependencies into separate archives, and if we encounter an archive with the same desired name, do not overwrite it. That way the admin could call archive on each bundle they care about and would ultimately get a directory filled with all unique bundles to move to the airgapped environment.

wordpress-v1.2.3.tgz
mysql-v5.7.14.tgz
nginx-v0.23.2.tgz

[carolynvs]

Duplicate of #554