Use retry_lock with explicit transaction in CreateDownstreamPipelineService

What does this MR do and why?

Switch from retry_lock_with_transaction to retry_lock with an explicit subject.transaction block in the else path since it performs multiple DB operations.

References

Edited by Panos Kanellidis

Merge request reports

Loading