snap-tempest:stable/caracal

Last commit made on 2024-04-30
Get this branch:
git clone -b stable/caracal https://git.launchpad.net/snap-tempest

Branch merges

Branch information

Name:
stable/caracal
Repository:
lp:snap-tempest

Recent commits

25d61c3... by Andrea Ieri <email address hidden>

release(caracal): update snapcraft.yaml (#165)

This commit has been generated by
canonical/snap-tempest-automation/actions/workflows/update-tempest-releases.yaml

Co-authored-by: aieri <email address hidden>

4d4bb1d... by Andrea Ieri <email address hidden>

release(caracal): update snapcraft.yaml (#160)

This commit has been generated by
canonical/snap-tempest-automation/actions/workflows/update-tempest-releases.yaml

Co-authored-by: aieri <email address hidden>

a8ae2e9... by Andrea Ieri <email address hidden>

Cleanup everything that was moved to canonical/snap-tempest-automation (#142)

3f891f3... by Robert Gildein

Support Juju 3.4 (#132)

* Support Juju 3.4

Changing to use of Juju 3.4 controller for testing instead of Juju 2.9.

* add concurrency

8131ca1... by Andrea Ieri <email address hidden>

Don't bundle uncommon plugins until we are sure they work well. (#133)

This is a rather harsh workaround to some plugins not respecting their
respective service being marked to be unavailable in tempest.conf

Co-authored-by: Samuel Allan <email address hidden>

0069b81... by Robert Gildein

 update codeowners to soleng (#117)

Update code owners to new group.

Co-authored-by: TQ X <email address hidden>

fa47095... by TQ X <email address hidden>

Rework and preserve comments in snapcraft.yaml during dependency updates (#122)

The comments regarding confluent-kafka will be overwritting by
tools/update_snapcraft.py when refreshing dependency versions
because pyYAML doesn't support comments. Use ruamel.yaml instead
with its round trip mode to solve the problem.

Also replacing the previous comment (since it's also in
requirements-manual.txt) with a new one that informs user that
some dependencies are automatically generated. This also gives user
a hint about where to check when they are unsure why a package like
confluent-kafka is added as a dependency.

675fb07... by Samuel Allan

Re-add comments re confluent-kafka version (#112)

These comments are important for context,
and will help in future when version updates are required,
and for rationale of rejecting auto dependabot updates, etc.

eae5f36... by Andrea Ieri

Use the auto-generated token.

Instead of manually managing personal access tokens as repo secrets, use
the auto-generated one. See
https://docs.github.com/en/actions/security-guides/automatic-token-authentication

7b9d512... by Andrea Ieri

Determine the latest compatible version via RSS feeds.

The tempest and tempest plugin metadata files in the releases[0] repository are
not updated continuously and therefore do not reflect the actual latest
compatible version for a given OpenStack release (see also the Tempest
nad Plugins compatible version policy[1]).
This commit switches to using the individual projects' RSS feeds as
source of truth as to which version should be picked; specifically, the
"{release}-last" tag if available, and the latest version tag otherwise.

[0] https://opendev.org/openstack/releases.git
[1] https://docs.openstack.org/tempest/latest/tempest_and_plugins_compatible_version_policy.html

Closes: #79