-
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
Allow non-default yaml loader and dumper #10032
Conversation
1a5a787
to
daac6c6
Compare
Codecov Report
Flags with carried forward coverage won't be shown. Click here to find out more. |
Just need to fix style, and rebase for #10035 |
daac6c6
to
8bde4b5
Compare
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 is fine as-is, or consider the suggestion below.
This reverts commit e01823a.
This reverts commit e01823a. Co-authored-by: Kylian Serrania <[email protected]>
What does this PR do?
Allow integrations to use a non-default YAML loader and dumper
How to use it
Inside an integration
Motivation
Needed for #9815 to use the python safe loader instead of the C one.
Additional Notes
This is changing the behaviour of the undocumented
disable_unsafe_yaml
agent option (which is true by default).Before:
After: