Aggregation and branching out multiple pipelines
A directory structure can be used to logically organize images that are dependent on each other. For example, a hardened enterprise Linux build with your organization’s single sign-on (SSO) or SSSD configuration may be required at the base level but then multiple application builds may be built from that base image. Structuring this as a directory tree makes automation super simple. You can recursively build directories and the directories within to build an entire library of images in order. Take this example, where there is a system base image directory and two nested system orchestrator images that install Kubernetes or Nomad on top of the base image:
$ tree system_base/ system_base/ ├── build.pkr.hcl ├── common.pkr.hcl -> ../common/common.pkr.hcl ├── system_kubelet │ ├── build.pkr.hcl │ ...
