Skip to content

chore: bump versions of things to support testing of this charm again - #16

Merged
addyess merged 4 commits into
mainfrom
chore/bump-test-actions
Dec 18, 2025
Merged

chore: bump versions of things to support testing of this charm again#16
addyess merged 4 commits into
mainfrom
chore/bump-test-actions

Conversation

@addyess

@addyess addyess commented Dec 18, 2025

Copy link
Copy Markdown

This pull request updates both the opa-audit-operator and opa-manager-operator projects to modernize dependencies, streamline testing workflows, and update documentation and code to use newer Juju commands. The changes improve compatibility with newer Ubuntu and Python versions, simplify integration tests, and ensure consistency in developer and user instructions.

CI/CD and Dependency Updates:

  • Updated GitHub Actions workflow to use newer Python versions (3.10, 3.12), latest Ubuntu runners, and upgraded action versions for better performance and compatibility. Also, the inclusive naming check now uses the canonical repository. (.github/workflows/tests.yaml) [1] [2] [3]
  • Updated requirements.txt in both operators to specify compatible version ranges for ops, lightkube, and replaced a Git dependency with a PyPI package for ops.manifest. (opa-audit-operator/requirements.txt, opa-manager-operator/requirements.txt)
  • Updated charmcraft.yaml in both operators to use Ubuntu 22.04 as the build and run base, dropping explicit support for Ubuntu 20.04 and some architectures. (opa-audit-operator/charmcraft.yaml, opa-manager-operator/charmcraft.yaml)
  • Added .charmcraft-channel file to specify the charmcraft channel for builds. (.charmcraft-channel)

Juju Command and Documentation Updates:

  • Updated documentation and status messages to use juju run instead of the deprecated juju run-action for executing actions, ensuring consistency with current Juju best practices. (opa-audit-operator/README.md, opa-audit-operator/src/charm.py, opa-manager-operator/README.md, opa-manager-operator/src/charm.py) [1] [2] [3] [4]

Integration Test Improvements:

  • Refactored integration tests in both operators to use the new unit.run_action(...).wait() API instead of invoking Juju CLI commands directly, simplifying test logic and improving reliability. (opa-audit-operator/tests/integration/test_charm.py, opa-manager-operator/tests/integration/test_charm.py) [1] [2] [3] [4] [5] [6]This pull request updates both the CI workflow and the operator dependencies to use newer versions and more consistent configurations. The main changes include upgrading Python and Ubuntu versions in CI, updating dependency version constraints, and aligning build environments for both operators.

CI/CD workflow updates:

  • Updated the GitHub Actions workflow to use Python 3.10 and 3.12 instead of 3.8 and 3.9, and switched to ubuntu-latest for integration tests instead of ubuntu-22.04. Also upgraded several GitHub Actions to their latest major versions and improved how the charmcraft channel is set. [1] [2]
  • Changed the inclusive naming check to use the canonical repository for consistency.
  • Added a .charmcraft-channel file to specify the charmcraft channel used in CI.

Dependency and build environment updates:

  • Updated requirements.txt for both opa-audit-operator and opa-manager-operator to specify version ranges for ops, lightkube, and ops.manifest, replacing the previous unconstrained or git-based dependencies.
  • Changed the charmcraft.yaml for both operators to use Ubuntu 22.04 as the build and run base, removing Ubuntu 20.04 and some architecture variants for consistency and modernization.This pull request updates the CI workflow and environment to use newer versions of dependencies and tools, improves compatibility with current Python and Kubernetes versions, and ensures that the proper charmcraft channel is used in integration tests.

CI workflow and dependency updates:

  • Updated the inclusive naming check workflow to use the new repository location (canonical/inclusive-naming instead of canonical-web-and-design/Inclusive-naming).
  • Updated Python versions used in tests to 3.10 and 3.12, removing 3.8 and 3.9, and set the integration test Python version to 3.12.
  • Upgraded GitHub Actions used in the workflow to the latest major versions (actions/checkout@v4, actions/setup-python@v6, and actions/upload-artifact@v4). [1] [2]

Integration test environment improvements:

  • Changed the Kubernetes provider channel from 1.26/stable to 1.34-strict/stable and made the charmcraft channel configurable by reading from the new .charmcraft-channel file. [1] [2]
  • Added .charmcraft-channel file with 2.x/stable to specify the charmcraft channel used during integration tests.

Copilot AI review requested due to automatic review settings December 18, 2025 17:30

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the GitHub Actions workflow for tests by bumping action versions to their latest releases and modernizing the Python and Kubernetes versions used in the test suite.

Key Changes:

  • Updated GitHub Actions to newer versions (checkout v3→v4, setup-python v4→v6, upload-artifact v2→v4)
  • Modified Python testing versions from 3.8/3.9/3.10 to 3.10/3.12
  • Upgraded MicroK8s channel from 1.26/stable to 1.34/stable

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .github/workflows/tests.yaml Outdated
@addyess
addyess force-pushed the chore/bump-test-actions branch from 1c3a3ea to ba296e5 Compare December 18, 2025 17:39
@addyess
addyess force-pushed the chore/bump-test-actions branch from fbd0b7d to d2ab10a Compare December 18, 2025 19:58
@addyess addyess changed the title chore: bump action versions in tests workflow chore: bump versions of things to support testing of this charm again Dec 18, 2025
@addyess
addyess merged commit 7e451a0 into main Dec 18, 2025
5 checks passed
@addyess
addyess deleted the chore/bump-test-actions branch December 18, 2025 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants