IssueRaiser

Enable globbing in "resources" field of kustomization.yaml

This is basically the same as https://github.com/kubernetes-sigs/kustomize/issues/119. Reopening, as the issue was closed. The reason for reopening is that we (Arrikto) believe that the reasons given for eschewing this feature don't really apply. It's also interesting that other use-cases mandating glob-like use have come up from the Kustomize team (although I feel the particular one could benefit from more explicit globbing): https://github.com/kubernetes-sigs/kustomize/issues/3204 **Is your feature request related to a problem? Please describe.** I want to automatically pick up new kustomizations inside a folder. For example, we have a structure like this: ``` user-resources ├── user1 └── user2 ... ``` and I want to have a kustomization file that automatically imports everything under `user-resources`: ```yaml resources: - path/to/user-resources/* ``` **Describe the solution you'd like** Kustomize should support globbing in resources. This feature is eschewed right now and the given reason is: > kustomize supports the best practice of storing one’s entire configuration in a version control system. > > Globbing the local file system for files not explicitly declared in the kustomization file at kustomize build time would violate that goal. > > Allowing globbing in a kustomization file would also introduce the same problems as allowing globbing in java import declarations or BUILD/Makefile dependency rules. > > kustomize will instead provide kustomization file edi

Posted by yanniszark on Nov 10, 2020, 10:52 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments

support (Sysadmin)

Enable globbing in "resources" field of kustomization.yaml

yanniszarkNov 10, 2020, 10:52 PM

This is basically the same as https://github.com/kubernetes-sigs/kustomize/issues/119. Reopening, as the issue was closed. The reason for reopening is that we (Arrikto) believe that the reasons given for eschewing this feature don't really apply. It's also interesting that other use-cases mandating glob-like use have come up from the Kustomize team (although I feel the particular one could benefit from more explicit globbing): https://github.com/kubernetes-sigs/kustomize/issues/3204 **Is your feature request related to a problem? Please describe.** I want to automatically pick up new kustomizations inside a folder. For example, we have a structure like this: ``` user-resources ├── user1 └── user2 ... ``` and I want to have a kustomization file that automatically imports everything under `user-resources`: ```yaml resources: - path/to/user-resources/* ``` **Describe the solution you'd like** Kustomize should support globbing in resources. This feature is eschewed right now and the given reason is: > kustomize supports the best practice of storing one’s entire configuration in a version control system. > > Globbing the local file system for files not explicitly declared in the kustomization file at kustomize build time would violate that goal. > > Allowing globbing in a kustomization file would also introduce the same problems as allowing globbing in java import declarations or BUILD/Makefile dependency rules. > > kustomize will instead provide kustomization file edi

Comments (0)

No comments yet. Start the discussion.

Comment on this issue