-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
strict parser is case-insensitive #753
Comments
I'm not sure if we want to use it I tried it and |
I submited an issue kubernetes-sigs/yaml#15 |
Interesting. Could you share a test case with |
kubernetes-sigs/yaml#19 is a potential fix, it actually seems to move along... maybe a good idea to try the patch? |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue has been open for a while, closing due to staleness but happy to reopen if the issue persists. |
…pshot Resize filesystem when restore a snapshot to larger size volume
We have enabled strict parsing to detect unknown keys, e.g.:
or:
But it appears that strict parser doesn't detect keys that had been misspelled by mix-case.
For example:
Subnets
aresUbnetS
, orNodeGroups
andnodegroups
, don't result in parser error.This looks like a bug in the parser, we should look into what causes it, and of course file a generic issue. We use
sigs.k8s.io/yaml
for this.The text was updated successfully, but these errors were encountered: