-
Notifications
You must be signed in to change notification settings - Fork 459
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
Prevent extra attributes in component configs #2978
Prevent extra attributes in component configs #2978
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
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.
Looks good!
If I understood correctly, people will still be able to use their Stack
and StackComponent
objects in Python with "faulty" configs for the time being. This is just blocking them from creating new "faulty" components or updating them in a bad way. We should maybe look into incorporating this into our design at some point in the future.
Added some small comments, feel free to ignore.
validation_config_class = type( | ||
config_class.__name__, | ||
(config_class,), | ||
{"model_config": {"extra": "forbid"}}, |
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.
At first, I thought that this line may overwrite the whole model_config
but it actually updated it. Good one!
@@ -75,7 +75,16 @@ def validate_stack_component_config( | |||
return None | |||
raise | |||
|
|||
configuration = flavor_class.config_class(**configuration_dict) | |||
config_class = flavor_class.config_class | |||
# Make sure extras are forbidden for the config class. Due to inheritance |
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.
As you mentioned in the description, for whatever reason, if a user sets the extra
to allow
, perhaps we can use a warning or a debug message here.
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.
The problem is, I can't even detect that right? Whether someone did it explicitly or whether it happened due to inheritance of BaseSettings
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.
True. Feel free to skip it.
Co-authored-by: Barış Can Durak <36421093+bcdurak@users.noreply.github.com>
Describe changes
Prevent extra attributes in the config classes of our stack components. Previously, this was defined in the
StackComponentConfig
parent class, but due to the inheritance order lots of our stack components allowed extra attributes. This PR fixes that by making sure extras are not allowed during stack component config validation.extra="allow"
in their configuration for some reason, this would now be ignored and extras will not be allowed. I can't think of any case where this would be necessary though.Pre-requisites
Please ensure you have done the following:
develop
and the open PR is targetingdevelop
. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.Types of changes