Enforce config types#61852
Conversation
cb5b9a2 to
4fa487a
Compare
Hi! I'm your friendly PR bot!You might be wondering what I'm doing commenting here on your PR. Yes, as a matter of fact, I am... I'm just here to help us improve the documentation. I can't respond to Okay... so what do you do? I detect modules that are missing docstrings or "CLI Example" on existing docstrings! So what does that have to do with my PR? I noticed that in this PR there are some files changed that have some of these Okay, what are they? Well, my favorite, is that since you were making changes here I'm hoping that If I can, then what? Well, you can either add them to this PR or add them to another PR. Either way is fine! Well... what if I can't, or don't want to? That's also fine! We appreciate all contributions to the Salt Project. If you Whatever approach you decide to take, just drop a comment here letting us know! Detected Issues (click me)Check Known Missing Docstrings...........................................Failed - hook id: invoke - duration: 1.06s - exit code: 1 Thanks again! |
4fa487a to
90c9502
Compare
fdcc461 to
42a39f4
Compare
waynew
left a comment
There was a problem hiding this comment.
Will check the rest of this after our meeting
What does this PR do?
Enforces config types as specified in the VALID_OPTS dictionary.
What issues does this PR fix or reference?
Fixes: #57873
Previous Behavior
Config types were not enforced in all cases. This allowed for a config type that was supposed to be a list that was passed a string would end up with something like
['s', 't', 'r', 'i', 'n', 'g']New Behavior
Does not allow config types where they cannot be cleanly converted to the expected type
Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.
Commits signed with GPG?
Yes