-
Notifications
You must be signed in to change notification settings - Fork 663
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
Add support for setting nodeps through cli and .ansible-lint #4280
base: main
Are you sure you want to change the base?
Add support for setting nodeps through cli and .ansible-lint #4280
Conversation
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Quality Gate passedIssues Measures |
@@ -132,6 +132,11 @@ def initialize_options(arguments: list[str] | None = None) -> None | FileLock: | |||
for k, v in new_options.__dict__.items(): | |||
setattr(options, k, v) | |||
|
|||
if options.nodeps is None or options.nodeps is False: |
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 not how env vars are supposed to work. When defined, they should always override the config options.
Preference order should always be: cli > env > config.
As proposed in #4258, it seems that having an option to set nodeps using the command line interface and/or .ansible-lint file to be desireable, so here is a simple implementation of it.