VMware Cloud Foundation: Automate and Operate [V9.0] — Lesson 3: Extensibility, event subscriptions, workflows, APIs, pipelines, source control, custom actions, secrets, versioning, and promotion between environments

Learning Objectives

• Break down the prerequisites, components, roles, and decision points involved in Extensibility, event subscriptions, workflows, APIs, pipelines, source control, custom actions, secrets, versioning, and promotion between environments.
• Complete a controlled activity for Extensibility, event subscriptions, workflows, APIs, pipelines, source control, custom actions, secrets, versioning, and promotion between environments and capture versioned automation workflow and promotion evidence.
• Challenge the result with an extensibility action exposing a secret through execution logs, then justify the corrective action.

Detailed Topics

• Extensibility
• Event subscriptions
• Workflows
• APIs
• Pipelines
• Source control
• Custom actions
• Secrets
• Versioning
• And promotion between environments
• Decision ownership, prerequisites, and acceptance evidence for Extensibility, event subscriptions, workflows, APIs, pipelines, source control, custom actions, secrets, versioning, and promotion between environments
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The demonstration traces Extensibility, event subscriptions, workflows, APIs, pipelines, source control, custom actions, secrets, versioning, and promotion between environments from requirement through execution and review. Learners see where evidence should be collected, how versioned automation workflow and promotion evidence supports validation, and which warning signs require investigation.

Hands-On Exercise

Work through a role-based scenario involving Extensibility, event subscriptions, workflows, APIs, pipelines, source control, custom actions, secrets, versioning, and promotion between environments. Validate the expected path, test “an extensibility action exposing a secret through execution logs,” choose the safest corrective action, and capture the reasoning and outcome in versioned automation workflow and promotion evidence.

1. Record the starting state, assumptions, identities, topology, and expected outcome.
2. Execute the planned workflow and collect evidence at each material checkpoint.
3. Test one valid path, one boundary condition, and the stated failure scenario.
4. Document the correction, retest result, rollback option, and follow-up owner.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for Extensibility, event subscriptions, workflows, APIs, pipelines, source control, custom actions, secrets, versioning, and promotion between environments.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how versioned automation workflow and promotion evidence should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

When Extensibility, event subscriptions, workflows, APIs, pipelines, source control, custom actions, secrets, versioning, and promotion between environments produces an unexpected result, reproduce the issue with the same scope, identity, workload, and time context. Inspect versioned automation workflow and promotion evidence, test whether “an extensibility action exposing a secret through execution logs” explains the evidence, apply the smallest reversible correction, and retest an unaffected path for regression.

Validation Checklist

• Configuration and source state used for Extensibility, event subscriptions, workflows, APIs, pipelines, source control, custom actions, secrets, versioning, and promotion between environments are versioned or otherwise traceable.
• Versioned automation workflow and promotion evidence shows both baseline and accepted result.
• Security, performance, dependency, and resilience side effects are considered where relevant.
• Recovery steps and handover notes are usable by an operations practitioner.

Lesson Outcome

Learners can apply Extensibility, event subscriptions, workflows, APIs, pipelines, source control, custom actions, secrets, versioning, and promotion between environments, explain the decisions made, and defend the result with versioned automation workflow and promotion evidence.