Brian Grant
Brian Grant
We could dedupe this with #3279
@justinsb One case where nested subpackages has come up without is Config Connector: #3344
kustomize has issues with the generator pattern also: https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/2299-kustomize-plugin-composition
Back to the original topic: Ensure functions make sense to me. That's similar to https://github.com/metacontroller/metacontroller functions. It could be a supported or at least recommended pattern, like variant constructors (#2590)....
For creating individual resources, imperative functions, CLI (e.g. kubectl create -o yaml), UI, etc. seems like the way to go.
An example: https://github.com/GoogleContainerTools/kpt-functions-catalog/tree/master/functions/go/enable-gcp-services This sets a blueprints.cloud.google.com/ownerReference annotation. Which prunes resources no longer needed. https://github.com/GoogleContainerTools/kpt-functions-catalog/tree/master/examples/enable-gcp-services-advanced#overview
Ah, the merge behavior was previously requested in #954
The question inevitably comes up regarding what to do when a generator function is updated. It depends on whether changing the behavior of existing uses is desirable or not. It...
The issue of pruning also applies to transformers that change resource identifiers, in the case that the identifier transformation is changed across revisions.
Thanks. Split out replacing the video into a separate issue: #3376