Class PlanRollback
java.lang.Object
com.eqixiac.equinix.design.plan.PlanRollback
Tears down resources a run created, in an order that cannot strand a billable Cloud Router.
- Every connection (provider connections and backbone links) is deleted, newest first. A delete that answers HTTP 404 counts as already gone.
- Each connection delete is then polled (with the
core/waitermachinery, on the options' clock and poll interval) until the connection readsDEPROVISIONEDor HTTP 404, for at mostdeleteTimeout. Fabric deletes connections asynchronously; deleting the Cloud Router while a connection is stillDEPROVISIONINGfails or orphans the router. - A Cloud Router is deleted only when every connection attached to it is confirmed gone, and its delete is polled the same way.
Routing protocols are removed by Fabric with their connection: they are reported removed when
their connection is, and orphaned when it is not. Anything that could not be removed is an
OrphanedResource with its uuid and the reason.
-
Method Summary
Modifier and TypeMethodDescriptionstatic RollbackReportrollback(FabricGateway fabric, List<CompletedStep> created, Map<String, List<String>> attached, ExecutionOptions options) Rolls back the given resources.
-
Method Details
-
rollback
public static RollbackReport rollback(FabricGateway fabric, List<CompletedStep> created, Map<String, List<String>> attached, ExecutionOptions options) Rolls back the given resources.- Parameters:
fabric- the Fabric clientcreated- the resources to remove, in creation orderattached- for each router key, the keys of the connections attached to it;nullwhen unknown, in which case any orphaned connection keeps every routeroptions- timeouts, poll interval and clock- Returns:
- what was removed and what was left
-