You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 10, 2023. It is now read-only.
As a user, I want to know some information about the package so that I can make a decision on if I should use it and how to use it. Some of this information is what will be installed in the cluster (resources), RBAC provided, description, authors, examples usage, next steps, pre-requisites.
I want to be able to get detailed information about an "available" package in a user consumable format. If the package provides some infrastructure component that expects users to create additional resources after the package has been installed (e.g. contour-operator expects the user to install a Contour CR) then, the package should provide an example so that the user does not need to go to the documentation. Additionally, it should contain a link to the documentation for the package.
It should define what's going to be installed, although this might be just a descriptive text, if there's a way to get a dry-run of what is going to be installed (as defined in https://github.com/vmware-tanzu/tce/issues/997 or https://github.com/vmware-tanzu/tce/issues/975).
The text was updated successfully, but these errors were encountered:
jorgemoralespou
changed the title
2. As a user, I want to know some information about the package so that I can make a decision on if I should use it and how to use it. Some of this information is what will be installed in the cluster (resources), RBAC provided, description, authors, examples usage, next steps, pre-requisites.
As a user, I want to know details about the package
Jul 7, 2021
As a user, I want to know some information about the package so that I can make a decision on if I should use it and how to use it. Some of this information is what will be installed in the cluster (resources), RBAC provided, description, authors, examples usage, next steps, pre-requisites.
I want to be able to get detailed information about an "available" package in a user consumable format. If the package provides some infrastructure component that expects users to create additional resources after the package has been installed (e.g. contour-operator expects the user to install a Contour CR) then, the package should provide an example so that the user does not need to go to the documentation. Additionally, it should contain a link to the documentation for the package.
It should define what's going to be installed, although this might be just a descriptive text, if there's a way to get a dry-run of what is going to be installed (as defined in https://github.com/vmware-tanzu/tce/issues/997 or https://github.com/vmware-tanzu/tce/issues/975).
It should also define the configuration that the package can accept (or complement with https://github.com/vmware-tanzu/tce/issues/972)
Status: In kapp-controller 0.20.0 some metadata is defined in a CR named Package and PackageMetadata.
Tanzu CLI Package plugin should expose these to the users. (Open/link issue)
kapp-controller related issue and kapp-controller issue
The text was updated successfully, but these errors were encountered: