Selective workflow restoration from Git in VMware Aria Automation Orchestrator
search cancel

Selective workflow restoration from Git in VMware Aria Automation Orchestrator

book

Article ID: 453014

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • Specific workflows were deleted from Aria Automation Orchestrator and are not found in "Deleted Items."
  • Workflows exist in a connected GitHub/GitLab repository.
  • The "Pull" action cannot be used because it would synchronize the entire branch and overwrite unpushed local changes.

Environment

  • VMware Aria Automation 8.x
  • VMware Aria Automation Orchestrator (vRO) 8.x

Cause

This is by design. The Git integration in VMware Aria Automation Orchestrator operates at the repository/branch level. There is no native functionality to perform a selective pull of individual files or workflows via the user interface.

Resolution

To restore specific workflows without performing a full branch synchronization, use the following "Sandbox Import" procedure:

  1. Prepare Sandbox: Use a separate test or sandbox VMware Aria Automation Orchestrator environment.
  2. Import XML: Retrieve the raw XML files for the specific workflows from the Git repository and import them into the sandbox environment.
    • Note: If a direct import is not visible, use the "Import workflow" system workflow from the vRO library.
  3. Create Package: Create a new package in the sandbox environment and add only the required workflows and their dependencies.
  4. Export Package: Export the newly created .package file to a local directory.
  5. Import to Production:
    • Log in to the Production VMware Aria Automation Orchestrator.
    • Navigate to Packages > Import.
    • Select the .package file created in step 4.
  6. Verify Elements: Complete the import wizard and verify that the specific workflows are restored.

Important Note on SecureStrings: Any SecureString attributes (e.g., passwords) are not stored in Git for security reasons. After restoration, you must manually re-enter these values in the workflow or configuration elements.

Additional Information

  • For more information on why secure strings are missing after sync, see KB 446735.
  • To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.