VMware Aria Automation: Install, Configure, Manage [V8.17] — Lesson 3: ABX, Orchestrator workflows, event topics, subscriptions, custom resources, secrets, APIs, pipelines, source control, error handling, and rollback

Learning Objectives

• Assess dependencies, controls, resilience, and the intended service outcome for ABX, Orchestrator workflows, event topics, subscriptions, custom resources, secrets, APIs, pipelines, source control, error handling, and rollback.
• Demonstrate the workflow and leave reproducible evidence in extensibility subscription test and recovery trace.
• Recommend a preventive improvement after resolving an event subscription firing twice and duplicating an external change.

Detailed Topics

• ABX
• Orchestrator workflows
• Event topics
• Subscriptions
• Custom resources
• Secrets
• APIs
• Pipelines
• Source control
• Error handling
• And rollback
• Decision ownership, prerequisites, and acceptance evidence for ABX, Orchestrator workflows, event topics, subscriptions, custom resources, secrets, APIs, pipelines, source control, error handling, and rollback
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The instructor builds a representative scenario for ABX, Orchestrator workflows, event topics, subscriptions, custom resources, secrets, APIs, pipelines, source control, error handling, and rollback, narrating each decision and showing how it contributes to a governed Aria Automation 8.17 service that connects infrastructure, publishes reusable templates, controls requests, supports extensibility, and manages day-two operations through clear ownership. The demonstration records extensibility subscription test and recovery trace so learners can compare design intent with observable behavior.

Hands-On Exercise

Complete a guided task covering ABX, Orchestrator workflows, event topics, subscriptions, custom resources, secrets, APIs, pipelines, source control, error handling, and rollback. Establish a working baseline, reproduce “an event subscription firing twice and duplicating an external change,” isolate the responsible configuration or dependency, apply a reversible fix, and update extensibility subscription test and recovery trace with before-and-after proof.

1. Map the current workflow and mark where the expected result can first be observed.
2. Run the scenario while preserving timestamps, object identifiers, and relevant output.
3. Apply a reversible correction only after evidence supports the cause.
4. Retest the original case plus an unaffected case and update the handover record.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for ABX, Orchestrator workflows, event topics, subscriptions, custom resources, secrets, APIs, pipelines, source control, error handling, and rollback.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how extensibility subscription test and recovery trace should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

For a failure in ABX, Orchestrator workflows, event topics, subscriptions, custom resources, secrets, APIs, pipelines, source control, error handling, and rollback, separate access, configuration, compute, network, storage, integration, and timing causes. Compare the observed sequence with extensibility subscription test and recovery trace; if “an event subscription firing twice and duplicating an external change” is confirmed, document why broader changes were rejected.

Validation Checklist

• Prerequisites and role permissions for ABX, Orchestrator workflows, event topics, subscriptions, custom resources, secrets, APIs, pipelines, source control, error handling, and rollback are confirmed before execution.
• The observed result agrees with expected values documented in extensibility subscription test and recovery trace.
• Exceptions are explained with evidence instead of being hidden by manual correction.
• The final record names the approver, monitoring point, and next improvement action.

Lesson Outcome

Learners can apply ABX, Orchestrator workflows, event topics, subscriptions, custom resources, secrets, APIs, pipelines, source control, error handling, and rollback, explain the decisions made, and defend the result with extensibility subscription test and recovery trace.