nats-operator:renovate/cryptography-41.0.x

Last commit made on 2024-02-01
Get this branch:
git clone -b renovate/cryptography-41.0.x https://git.launchpad.net/nats-operator

Branch merges

Branch information

Name:
renovate/cryptography-41.0.x
Repository:
lp:nats-operator

Recent commits

ce00139... by Renovate Bot <email address hidden>

chore(deps): update dependency cryptography to v41.0.7

6e4a671... by Jatin Arora

fix(tests): Ignore a timing issue between `client` and `ca-client` relation

This commit fixes the tests for TLS where a timing issue can happen when
both the Client and the CA Client relation for the NATS charm are
scheduled. If the Client relation forms first a non-TLS url is shared
with the remote unit as NATS had been configured with it when it
started. But by the time the connection was made NATS was reconfigured
to use the TLS information.

5bbff68... by Jatin Arora

test: increase wait timeout for applications to become active

The tests sometimes fail by timing out as the model sometimes takes
longer than expected to deploy.

3677b46... by Jatin Arora

feat(test): add upgrade test

This commit adds a test which checks the upgrade from older charm
`nats-charmers-nats` deployed on `jammy` to this newer charm.

9145e02... by Jatin Arora

fix(charm): restore state when upgrading from the older version of the charm

This commit fixes the case where the newer ops charm when being used to
update/refresh the older charm lost the state carried by the reactive
charm. This commit restore the local state for the `ca_client` relation
by fetching the data back from the relation.

5b97a96... by Jatin Arora

fix(ci): fix the typo to the secret name

This commit fixes the secret name from CHARMCRAFT_TOKEN to
CHARMHUB_TOKEN.

88b3c71... by Simon Fels

Merge pull request #34 from jat-canonical/master

fix(ci): fix name for charmcraft secret

6443c77... by Jatin Arora

fix(ci): fix name for charmcraft secret

This commit fixes the name of the charmcraft secret configured.

bb582e8... by Jatin Arora

fix(ci): move publishing from Github to Launchpad

This commit removes the publishing step from Github as we do not have
arm64 runners available on Github Actions. We need to build arm64
compatible charms which can be done on Launchpad and the publishing to
`latest/edge` can be done from there itself.
However, the promotion of the charm can still be done once uploaded to
charmhub. So we are keeping the promotion jobs as is.

709abc9... by "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com>

chore(deps): update renovatebot/github-action action to v39.1.0