Rubén Pérez
03/31/2023, 10:15 AMcontract_requiring_verification_published .
Once we have done this, both Webhooks will be triggered by any contract change, resulting in requests to both CI systems. During the migration process, we expect that every repository is either using one CI system or the other mainly, and not using both other than for initial migration tests.
Taking that into account, that would made the Webhook execution information shown in the Borker UI not ideal, because it will probably stay as "Retrying" some time, and then shown as "Failed" because it will not be able to trigger one od the CI's executions.
Do you know if there is a way to get a "smother" migration, and hence not get that feedback from the UI? I mean seeing Webhook executions failed because it will try to trigger both Webhooks, and we expect one to always fail.Rubén Pérez
03/31/2023, 10:15 AM