search

carvel-dev / kapp-controller

Continuous delivery and package management for Kubernetes.
https://carvel.dev/kapp-controller
Apache License 2.0
269 stars 105 forks source link

Kapp-controller value schema for packages should show required configuration #474

Open renuy opened 2 years ago

renuy commented 2 years ago

As part of kctrl (kapp-controller CLI) command - kctrl package available list", there is requirement to show whether there is a required configuration that should be provided (e.g. external-dns does not work without providing the required data-values).

  1. Can we derive this information from value schema in kapp-controller package?
  2. Will adding certain meta-data help derive this information?

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible" 👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

danielhelfand commented 2 years ago

The valuesSchema property isn't very structured on the kapp-controller side. It really could be anything, including JSON.

I am wondering if this would be an ask to ytt to see if this information could be added to the generation process. Then kctrl could use information about whether the field is required. Not sure how this looks according to the OpenAPI schema spec, but I can follow up on that.

joe-kimmel-vmw commented 2 years ago

@pivotaljohn - does ytt support the openapi "required" block"? seems like that would be what's called for in this kctl feature being discussed.

neil-hickey commented 1 year ago

@renuy any idea of where this issue is today? Still a problem that we want to figure out? Or was a workaround found in kctrl?