🐛Pydantic V2: interpretation of "None" changed #6820
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What do these changes do?
Pydantic V1 version of EC2 settings was interpreting the string
None
as pythonNone
. This changed with the new version of the ec2 settings.pyThis PR ensures the string
null
is set in case it is pythonNone
.Due to this issue, the autoscaling service running in the private clusters is disabled.
Related issue/s
How to test
Dev-ops checklist