-
Notifications
You must be signed in to change notification settings - Fork 844
Relax key validation of sni.yaml #8549
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
Conversation
|
A potential problem is that you misspell a key for which there is a default value. Then you are running with the default value and will see no problem indication in diags.log. Should we use Warning instead of Note? |
6427bff to
b6111a2
Compare
b6111a2 to
ebaadb2
Compare
|
Please take another look. I followed the advice we talked about at the weekly bug scrab.
|
ywkaras
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR checks failing
hmm, something wrong with the ci system. |
|
All green, it's ready! |
(cherry picked from commit a13fd3d)
(cherry picked from commit a13fd3d)
|
Cherry-picked to v9.1.x branch. |
* asf/9.2.x: Updated ChangeLog docs: fix fedora install notes and spelling issues (apache#8537) Docs: Fix default value of proxy.config.ssl.handshake_timeout_in (apache#8574) Partial of revert "Cleanup generated LDFLAGS for jemalloc (apache#8285)" (apache#8533) TSUserArg: add value type checking (apache#8550) Relax key validation of sni.yaml (apache#8549) Clear random header value by AIO read error (apache#8559) Fixes macOS arm64 builds (again) (apache#8556) Traffic Dump: Use the correct transaction user index (apache#8548) combo_handler: Initialize User Arg Index in TSRemapInit (apache#8551) backout down parent retry limiting in parent selection and nexthop (apache#8546)
(cherry picked from commit a13fd3d)
For the forward compatibility of new keys.
Background
When ATS reads the
sni.yamlfile, it checks the keys of the yaml. This is a bit annoying when you deploy a new key to the env which has old and new versions of ATS.IMO, just ignoring "unknown keys" is fine. Because the function touches the node by defined keys. Any concerns?