Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cloudcode.yaml.crdSchemaLocations wildcard (*/**) path support #979

Open
codysmithd opened this issue Dec 13, 2024 · 0 comments
Open

cloudcode.yaml.crdSchemaLocations wildcard (*/**) path support #979

codysmithd opened this issue Dec 13, 2024 · 0 comments
Labels
kind/enhancement New feature or request

Comments

@codysmithd
Copy link

Use case
Working on a large project, with lots of CRDs in lots of YAML definition files in a deeply-nested build output directory.

Feature
The existing crdSchemaLocations would have support for globs, and visual-studio-code settings built-ins like ${workspaceFolder}.

e.g.

"cloudcode.yaml.crdSchemaLocations": [
    "${workspaceFolder}/bazel-output/crds/**/*.yaml"
 ]

Which would match files:

  • bazel-output/crds/myThing/definition.yaml
  • bazel-output/crds/otherThing/nestedDeeper/definition.yaml
    etc.

Ideally, this would also be tolerant of YAML files that match the glob and are not CRDs too (and would just ignore them).

@maxrandolph maxrandolph added the kind/enhancement New feature or request label Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants