phani

> Function parameter descriptions and declarative validation are needed. This is something in our radar already. We are trying to figure out the right UX for package publishers to provide...

@natasha41575 Let me know if you have cycles to pick this up. @KnVerey Since cmd/config commands are alpha in kustomize, please let us know the best way to deprecate them...

Good point. Accepting this as a feature request. But it will be delivered as part of long term changes as it would break backwards compatibility.

@mikebz This is slightly different from what I am working on. I am tracking this issue and update it accordingly.

@StarpTech Thanks for filing the issue. This must be related to parsing template structures in yaml.

@natasha41575 @etefera This is a good candidate to understand more about kyaml parsing. If you don't have cycles I can pick this up. cc @mikebz

@seh Have you tried modifying the yaml like this ``` apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization patches: - target: kind: Something patch: - op: add path: placeholder value: known ``` This works

@seh @msonnleitner There are 2 issues here. 1. kpt can't interpret value strings as nested yaml nodes. 2. kustomize needs patch to be a string. @monopole @Shell32-Natsu Can patches be...

I think it would be confusing to just fetch a package using `kpt pkg get` and making the functionality equivalent to `git clone`. `kpt pkg get` does many more things...

You mean `kpt1 pkg get` should fetch any package, run fix ? That would be confusing and doesn't fall under the contract of get command. We should have migration to...