Giovanni Liva

Thank you @philipp-hinteregger! I'll assign the ticket to you :)

The team decided to change the `/sequence/{project}` to add a new parameter `service`. Furthermore, check if there could be the possibility that a sequence is blocked by another with the...

After a discussion with @thschue, we agreed that the problem cannot be solved easily on the control plane. Instead, the integrations should provide a unique name to facilitate the installation...

Hey @shardulsrivastava sure thing! Thanks for helping us out :)

> In a multi-project scenario, this means that one misbehaving project / sequence will block all other projects / sequences. Please consider queing per project / sequence. The queue is...

> I wasn't aware about this, and it's not reflected in the issue. The issue reads like there is a global queue. To avoid further confusion, could you update the...

With the change of the shipyard-controller to make use of JetStream, this ticket might be obsolete. Nevertheless, the `POST /api/v1/event` might get a new error code from NATS if the...

Hi @joshua-giumelli-deltatre do you have only Keptn installed into your cluster? Could it be that you have an external job that rotates the secrets?

Thank you @AbhijithGanesh, the more eyes on this bug the easier is to spot why there was a drift :)

The team agrees on removing `bridge.installationType` helm flag and retrieving this data from the `GET /metadata` endpoint based on the `continuous-delivery.enabled`.