Properly handle workflows rollback and execution destroy

[rtortori]

Currently it seems if we terraform destroy an execution we remove it from the state file and clear it from the Requests in Intersight.

Ideally, in this specific context a Terraform destroy should:

• Optionally avoid the deletion in Intersight (in case we want to keep the list of executions) if a specific parameter is set by the user in the resource
• Automatically rollback the workflow if rollback_action = "Enabled" maybe by calling the code present in the intersight_workflow_rollback_workflow resource.

Sample TF Code

resource "intersight_workflow_workflow_info" "claimhttp" {
  name         = "claimhttp"
  action = "Start"
 
  input = {
    "name" = "httpbin"
    "endpoint" = "httpbin.org"
  }

  organization {
    object_type = "organization.Organization"
    moid        = var.organization
  }
  workflow_definition {
    object_type = "workflow.WorkflowDefinition"
    moid        = var.workflow_moid
  }
}

[code-lucidal58]

@rtortori If a workflow triggering resource is destroyed, then the corresponding workflow is also deleted. It can be modified to just terminate the workflow if it is still running. Today, it is deleted as well. If I understand you correctly, I think this is the correct approach for "deleting" workflows, i.e. just terminate.

Regarding the rollback action, the creation of resources cannot be controlled through logic. Rather, you can create a dependency between workflowInfo and RollbackBackWorkflow resources. The RollbackBackWorkflow's action will depend on the value of one of the properties (rollback enable) of workflowInfo resource.