-
Notifications
You must be signed in to change notification settings - Fork 242
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
CumulusCI.yml linter based on Pydantic #1624
Conversation
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.
This looks good to me. Thanks for letting me walk myself through the code with you @prescod!
45a3851
to
d4175ae
Compare
@prescod A big part of why I let this one stall out is because I'm nervous about breaking things because there is something used in the wild that we missed including in the validator. Could we start with this in a mode that is either opt-in or logs warnings rather than aborting, so that we have a way to try it out and find the gaps? |
If my time machine is properly functioning then that's how it already works. :) It returns the data along with printing warnings about problems. This iteration of it does not block people from using incorrect CCI.yml files. The Pydantic model is used entirely in an advisory way. |
Co-authored-by: David Glick <dglick@salesforce.com>
Validates CumulusCI.yml files now. If they do not match the pattern, it will generate a warning.
Incorporates the NBSP cleanup tool from the other branch.