Skip to content
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

Rename meta-unsupported-ansible to meta-runtime and correct its logic #3000

Merged
merged 7 commits into from Feb 9, 2023

Conversation

alisonlhart
Copy link
Contributor

@alisonlhart alisonlhart commented Feb 9, 2023

Refactoring and renaming meta-unsupported-ansible rule to meta-runtime for a more accurate name.

Added SpecifierSet (valid version with operators) check for the requires_ansible key value. This will verify that the version value is a valid version under Pythonic requirements.

Examples:

Valid:

---
requires_ansible: ">=2.20.0"

Invalid:

---
requires_ansible: "2.20.0"

Added documentation of this to the rule .md file and renamed .md file to meta-runtime.md to match.

Fixes #2999

@alisonlhart alisonlhart requested review from a team as code owners February 9, 2023 00:38
@ssbarnea ssbarnea changed the title src/rules/meta-runtime.py: Renaming rule, adding check for version Rename meta-unsupported-ansible to meta-runtime and correct its logic Feb 9, 2023
@ssbarnea ssbarnea added the bug label Feb 9, 2023
@ssbarnea ssbarnea self-assigned this Feb 9, 2023
@ssbarnea ssbarnea merged commit 26a12aa into ansible:main Feb 9, 2023
@alisonlhart alisonlhart deleted the meta_runtime_rule_extend branch February 10, 2023 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

meta-runtime (meta-unsupported-ansible): Refactor and adding SpecifierSet check
2 participants