Here’s an update on the work done by the IS Charms team in the last two weeks:
- Fixed a bug caused by the external jenkinsapi library on Jenkins when safeRestart is called while a job is running.
- Synapse operator initial version added.
- Fixed an issue causing Redis k8s operator to not propagate the IP changes if a node is restarted in the same node that was affecting Indico.
- Added Traefik support to Synapse operator.
- Created https://github.com/canonical/charm-relation-interfaces/pull/81 “Express relation data for prometheus_scrape as string rather than native JSON object”
- Fixed an issue with the GitHub runner security policy checks where jobs that aren’t pull requests were raising 500 errors. They should now report missing/ empty data instead: https://github.com/canonical/repo-policy-compliance/pull/239
- Modified the operator-workflows so that the artifacts generated during integration testing are the same published to charmcraft. This not only increases speed but also improves the reliability of the workflows. To support publishing, strict checks must be configured in the repositories
- Fixed bug with COS modules in integration tests in wordpress-k8s-operator
- Added configuration option to specify update time range in jenkins-k8s-operator
- Convert github-runner-operator to use RAM as disk for the self-hosted runner instances.
- Added mechanism to prevent change of server_name to Synapse operator.
- Published version of Synapse operator to Charmhub.