Skip to content

Commit

Permalink
tests: use mysql-k8s from 8.0/stable instead of 8.0/edge (#243) (#246)
Browse files Browse the repository at this point in the history
In 8.0/edge a strict  was introduced, making this charm impossible to deploy with
a juju version == 3.5.{0,1}. Since this version is the one we use in our CI, we have to pin
mysql-k8s to its stable version as it does not have these restrictions.
  • Loading branch information
DnPlas authored Jul 1, 2024
1 parent fbc5c56 commit 7fa0a78
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion tests/integration/test_charm.py
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,7 @@
METADATA = yaml.safe_load(Path("./metadata.yaml").read_text())
CHARM_NAME = METADATA["name"]
RELATIONAL_DB_CHARM_NAME = "mysql-k8s"
RELATIONAL_DB_CHANNEL = "8.0/stable"
OBJECT_STORAGE_CHARM_NAME = "minio"
PROMETHEUS_CHARM_NAME = "prometheus-k8s"
GRAFANA_CHARM_NAME = "grafana-k8s"
Expand Down Expand Up @@ -185,7 +186,7 @@ async def test_add_relational_db_with_relation_expect_active(self, ops_test: Ops
RELATIONAL_DB_CHARM_NAME,
# We should use `8.0/stable` once changes for
# https://github.com/canonical/mysql-k8s-operator/issues/337 are published there.
channel="8.0/edge",
channel=RELATIONAL_DB_CHANNEL,
series="jammy",
trust=True,
)
Expand Down

0 comments on commit 7fa0a78

Please sign in to comment.