viccuad
commented
1 year ago ~~We have defined the usage of artifacthub-pkg.yml fields in UI, and how to derive them from metadata.yml.
We have hand-crafted artifacthub-pkg.yml for the policies to unblock the UI work.~~
Still, we are missing automating the generation of
artifacthub-pkg.yml:- [ ] RFC for implementation approach and alternatives: https://togithub.com/kubewarden/rfc/pull/15
- [ ] https://togithub.com/kubewarden/kwctl/issues/418
- [ ] Document the usage of the new
kwctl scaffold artifacthub-pkg for policy authors that want to publish in artifacthub.io- [ ] Update GHA workflows to use the new kwctl command, and, either generate the new
artifacthub-pkg.yml, or make sure it has automatically been updated and committed, prior to release- [ ] Update policy templates if needed, so future community policies are easier to publish on artifacthub
- [ ] Re-release policies
- [ ] Reach out to community policies and propose changes so they are published. See list in https://togithub.com/topics/kubewarden-policy (e.g: https://togithub.com/nlamirault/probes-policy, https://togithub.com/nlamirault/disallow-default-namespace-policy, ..)
flavio
Once the metadata in ArtifactHub contains the rules for each policy, the rule sets when creating a policy will need to be auto-generated, and possibly limit the ability to add more rules.
Acceptace criteria
kwctl scaffold. Potentially: settings, rules, mutating, backgroundAudit. (e.g: here)