Sorry for the delay. The theory is now confirmed, it was only an issue of using a Juju version (3.1.6) on the pipelines, that did not yet support `secret-changed` event to be sent to the secret owner.
The bug can be closed, it is not a bug :-)
Sorry for the delay. The theory is now confirmed, it was only an issue of using a Juju version (3.1.6) on the pipelines, that did not yet support `secret-changed` event to be sent to the secret owner.
The bug can be closed, it is not a bug :-)