kpack-cli
kpack-cli copied to clipboard
kp (cluster)builder status should display tree order output
Currently, the output from kp (cluster)builder status only shows the top level order of a builder. However, pack inspect-builder will show the entire tree like hierachy of a builder's buildpacks. kp should show the same information to users so that they can better understand and diagnose kpack builders.
would love to see the screenshot if you have it !
Detection Order:
├ Group #1:
│ └ paketo-buildpacks/[email protected]
│ └ Group #1:
│ ├ paketo-buildpacks/[email protected]
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected]
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ └ paketo-buildpacks/[email protected] (optional)
├ Group #2:
│ └ paketo-buildpacks/[email protected]
│ └ Group #1:
│ ├ paketo-buildpacks/[email protected]
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ └ paketo-buildpacks/[email protected] (optional)
├ Group #3:
│ └ paketo-buildpacks/[email protected]
│ ├ Group #1:
│ │ ├ paketo-buildpacks/[email protected]
│ │ ├ paketo-buildpacks/[email protected]
│ │ ├ paketo-buildpacks/[email protected]
│ │ └ paketo-buildpacks/[email protected]
│ ├ Group #2:
│ │ ├ paketo-buildpacks/[email protected]
│ │ ├ paketo-buildpacks/[email protected]
│ │ └ paketo-buildpacks/[email protected]
│ └ Group #3:
│ ├ paketo-buildpacks/[email protected]
│ └ paketo-buildpacks/[email protected]
├ Group #4:
│ └ paketo-buildpacks/[email protected]
│ ├ Group #1:
│ │ ├ paketo-buildpacks/[email protected]
│ │ ├ paketo-buildpacks/[email protected]
│ │ └ paketo-buildpacks/[email protected]
│ ├ Group #2:
│ │ ├ paketo-buildpacks/[email protected]
│ │ ├ paketo-buildpacks/[email protected]
│ │ ├ paketo-buildpacks/[email protected]
│ │ └ paketo-buildpacks/[email protected]
│ └ Group #3:
│ ├ paketo-buildpacks/[email protected]
│ └ paketo-buildpacks/[email protected]
├ Group #5:
│ └ paketo-buildpacks/[email protected]
│ └ Group #1:
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ └ paketo-buildpacks/[email protected]
├ Group #6:
│ └ paketo-buildpacks/[email protected]
│ └ Group #1:
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected] (optional)
│ ├ paketo-buildpacks/[email protected]
│ ├ paketo-buildpacks/[email protected] (optional)
│ └ paketo-buildpacks/[email protected]
├ Group #7:
│ └ paketo-buildpacks/[email protected]
├ Group #8:
│ └ paketo-buildpacks/[email protected]
└ Group #9:
└ paketo-buildpacks/[email protected]