Creating deployments may lead to Deployments::SuccessWorker running twice

The following discussion from !18755 (merged) should be addressed:

  • @dosuken123 started a discussion:

    @yorickpeterse I think this triggers the Deployments::SuccessWorker twice. Onc is when deployment is created via API, one is when status was updated to success. Can we remove AfterCreateService from Deployments::CreateService, so API and non-API paths will behave the same?

Assignee Loading
Time tracking Loading