If you choose to, Git can be used to source control your vRO code, thereby allowing you to back up, track, and manage changes to the workflow code independently of vRO. Committing a version to the repository will include workflows and their dependencies (actions and packages).
You need to add Git repositories to vRO (Aria Orchestrator) to provide it with access to the necessary repositories. This post has instructions for adding repositories to vRO and pushing code to them.
Adding Repositories to vRO
You would need the following handy before you add a repository:
Repository URL
Username with permissions on the repository
Access token generated for the repository.g
Name of the remote branch. (VRO assumes this to be ‘main,’ ensure to specify the correct branch)
The following procedure can be used to add a repository to vRO:
Step 1: Log in to vRA - Cloud Service Console and select Orchestrator from My Services.
Step 2: On the Orchestrator page, navigate to Administration | Git Repositories and click on ADD REPOSITORY.
Step 3: Supply the repository URL, username, and the access token obtained from your repo server. Click VALIDATE to attempt a connection to the repository. If successful, a temporary banner will appear incidating the same.
Step 4: On a successful connection to the repository, an option to select a remote branch will appear. Select an existing branch (in this case, ‘master’) and choose to make the repository active.
Keep in mind there can only be one active repository.
Note: Specifying an invalid branh here might not show an error, but when you attempt to push code to the repo, it will fail with an error indicating that the remote branch does not exist. Error: Remote branch ‘’main’ not found in upstream origin, does not exist on the remote server.
Step 5: The new repository should now appear active under Administration | Git Repositories.
Pushing vRO Content to a remote branch
Now that you have created and activated a new repository, navigate to Administration | Git History
At this point, you could pull the remote branch or push content to it. Since this is a new repository, I will push content to the remote branch.
On the “Push Changes to Remote Branch” window, select items to be pushed and supply a Commit title, a version, and an optional commit message. In this example, I am pushing all items since there is an empty remote repository.
Once done, Administration | Git History should show your commit.
Your repository on your Git host should list the contents with the commit title.
You could also push code directly from a workflow/action that you have modified.
For instance, you have made some changes to a workflow. To push the changes to the remote repository, click VERSION.
On the Push New Vession window, input a Commit title and a version and click PUSH.
Once complete, your latest commit will appear one the left pane.
Your Git server should also report the commit activity.
Also, the repository’s contents should list the changed item with the commit title.
Commentaires