Aleksei Sviridkin 9e6465d093 fix(rabbitmq): scope the topology-object refusal to this release ...

A tenant namespace holds every RabbitMQ application the tenant runs, and
the listing enumerated all of them. A second instance with users kept the
first from ever closing its listeners, and the refusal named the other
application's objects and told the operator to delete them. The mechanism
behind the refusal does not reach that far either: a sibling's topology
objects are reconciled through their own broker, whose listeners this flag
leaves alone.

Read spec.rabbitmqClusterReference.name and keep only the objects that
name this release. The hand-written fixture gained the reference it was
missing, which is what hid the gap, and a sibling release now has a case
of its own.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-09-04 11:45:04 +03:00

..

apps

fix(rabbitmq): scope the topology-object refusal to this release

2026-09-04 11:45:04 +03:00

core

fix(valkey): add cozystack-engine dependsOn edge to the PackageSource

2026-09-01 11:44:29 +04:00

extra

docs(etcd): note that affinity is not applied to existing members

2026-09-01 12:47:46 +03:00

library

fix(cozy-lib): convert micro and nano quantities instead of zero

2026-08-16 22:20:17 +03:00

system

docs(rabbitmq): carry the TLS consequences to where the toggle is rendered

2026-09-04 11:28:04 +03:00

tests/cozy-lib-tests

fix(cozy-lib): convert micro and nano quantities instead of zero

2026-08-16 22:20:17 +03:00