Custom content is not available within Git history after migrating vRealize Orchestrator 7.5 to vRealize Orchestrator 8.x

Products

• VMware Aria Suite

Issue/Introduction

In vRealize Orchestrator 7.5, by default, content without version history is migrated without version history to 8.x.

Symptoms:

• Git integration is configured within your environment: Configure a Connection to a Git Repository
• After migration of a vRealize Orchestrator 7.5 instance to 8.x, when you add an external Git repository, migrated custom content is not available within the Git history and you are unable to push it to the Git repository.
• You only see system content migrated from vRealize Orchestrator 7.5.

Environment

VMware vRealize Orchestrator 8.x
VMware vRealize Orchestrator 7.5.x

Cause

In vRealize Orchestrator 7.5, the content has no version history, after migration to vRealize Orchestrator 8.x, the content will not be tracked in Git as local changes.

Resolution

See the workaround below for additional information.

Workaround:
After you add an external Git repository, post migration, make sure you edit and save your custom content before you make the initial push to Git.