feat: func config envs - interactive prompt

[zroubalik]

Signed-off-by: Zbynek Roubalik zroubali@redhat.com

Interactive prompt for managing function configuration - this PR adds Environment variables

func config envs - list configured Environment variables

func config envs add- starts interactive prompt, wizard that let's you add Environment variable to the configuration. It does a lookup for existing Secrets and ConfigMaps in the cluster and namespace.

func config envs remove

• starts interactive prompt, wizard that let's you remove Environment variable from the configuration.

Relates: #362

config_envs.mp4

[lkingland]

Looks good to me!
One thing I did not mention earlier, but may bear at least highlighting, is that with the addition of these interactive commands which hit the kubernetes API, our CLI is now coupled with the kubernetes API (rather than having that clean layer of func in between). But I am conflicted if this is really an existential problem, as it is coupling in order to ease the creation of that clean intermediary layer.

Just worth mentioning I suppose, because it provides a good example of challenging my desire to maintin the "purity" of the CLI, but for a clearly user-assisting reason.

[zroubalik]

Looks good to me!
One thing I did not mention earlier, but may bear at least highlighting, is that with the addition of these interactive commands which hit the kubernetes API, our CLI is now coupled with the kubernetes API (rather than having that clean layer of func in between). But I am conflicted if this is really an existential problem, as it is coupling in order to ease the creation of that clean intermediary layer.

Just worth mentioning I suppose, because it provides a good example of challenging my desire to maintin the "purity" of the CLI, but for a clearly user-assisting reason.

You are right, I had the same concern, but I think that this is inevitable given the fact that we are going to part of Knative 🤷‍♂️

[lance]

You are right, I had the same concern, but I think that this is inevitable given the fact that we are going to part of Knative

True - but it would be nice ultimately to have something like grid that proxies these API calls to Kube/Knative or some other platform. But for now going directly against the API is fine I suppose.

[lance]

I like it - sorry about the prompt impl Luke!