I am using the octopus.client library in which I am making multiple changes during a complex process. (Creating multiple environments, adding multiple machines, creating lifecycles, adding environments to different phases of the lifecycle, adding channels to projects, adding lifecycles to the channel etc).
This process involves making changes to other databases as well.
Ideally I would like to wrap the whole process up in a series of transactions that if the all steps are successful on all databases, they are committed, but if any are not successful on any database, they are all rolled back.
Does the octopus.client library offer the concept of transactions?