Standardize config folders structure #3821
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
triage/blocked
Milestone
What do you want to happen?
I think would be good to standardize the structure of folders generated under
config
folder. Example:crd
folder hasbases
foldersamples
folder does not havebases
folderMy motivation was an automation I added to a project, which was easier to add to folders that had
bases
folderI believe the only change, would be that
kustomization.yaml
files would change resources section from- file_name
to- bases/file_name
I also believe this problem is NOT A PRIORITY, just a nice to have feature
Extra Labels
No response
The text was updated successfully, but these errors were encountered: