New to Kubepack? Please start here.

Scenario-6

This docs explain how Pack’s fork works.

This section explain test-6.

If you look into this test’s manifest.yaml file.

$ cat manifest.yaml

package: github.com/kubepack/pack/docs/_testdata/test-6
owners:
- name: Appscode
  email: [email protected]
dependencies:
- package: github.com/kubepack/kube-a
  branch: test-6
  fork: https://github.com/kubepack/kube-d.git
- package: github.com/kubepack/kube-b
  branch: test-6
  fork: github.com/kubepack/kube-c

See image below, which describe whole dependency.

Explanation of image:

1. kube-c and kube-d both patch repository kube-a and kube-b.
2. This test depends on two repository.
   • fork kube-d of kube-a repo.
   • fork kube-c of kube-b repo.

Now, $ kubectl plugin pack dep command get the dependencies and place under manifests/vendor folder. pack pulls kube-a from fork kube-d and kube-b from fork kube-c.

Next Steps

• Want to publish apps using Kubepack? Please visit here.
• Want to consume apps published using Kubepack? Please visit here.
• To learn about manifest.yaml file, please visit here.
• Learn more about pack cli from here.