feat: Adopt uv for dependency management#5
Merged
Conversation
Replace the requirements.txt / build-requirements.txt pair with a single pyproject.toml managed by uv, and move to the latest Python and Ansible that work with these playbooks. - Python 3.14 (pinned via .python-version) - ansible 14 (ansible-core 2.21), kubernetes client 35 (k8s 1.35) - yamllint and ansible-lint as dev dependencies - Drop awscli, boto3, jmespath and openshift (unused by these playbooks) - CI now installs via astral-sh/setup-uv and runs the linters with uv run - Ignore .venv in yamllint and git - Document the uv workflow in README.md and add CLAUDE.md Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Replaces the
requirements.txt/build-requirements.txtpair with a singlepyproject.tomlmanaged by uv, and moves to the latest Python and Ansible that work with these playbooks..python-versionyamllintandansible-lintas dev dependenciesawscli,boto3,jmespathandopenshift— none are used by these playbooks (cluster auth is via theK8S_AUTH_*env vars injected by AWX). Shout if your AWX/EKS setup needsawscli/boto3for token minting and I'll add them back.astral-sh/setup-uvand runs the linters withuv run.venvignored by yamllint and gituvworkflow inREADME.md; also adds aCLAUDE.mdVerification
uv lock --check— cleanuv run ansible-playbook --syntax-check site.yaml— passesuv run yamllint .and the*.yaml.j2pass — both cleank8smodule resolves (kubernetes.coreships with theansiblepackage)🤖 Generated with Claude Code