For resource actions, these can be manually removed and re-added in the Aria Automation UI, this will resolve the conflict with the vRO integration id.
To resolve the issue with existing custom resource types that are referenced in custom forms the integration id can be updated to the new id using the forms service API:
1. Document the new vRO integration ID:
Open browser tools Network console and navigate to the newly re-added vRO integration. Cloud Assembly -> Infrastructure -> Integrations
The new Orchestrator integration id will be visible in the browsers call to the /iaas/api/integrations request url, see example below from a lab environment:
Request URL: https://<vRA-FQDN>/iaas/api/integrations/dcd46018-9712-4fe5-b825-59f58bae2e49?apiVersion=2021-07-15
The vRO integration ID also visible in the url of the browser if you navigate to the integration in the UI. The id is the last string after 'edit%2F'
2. Generate a bearer token to authenticate via API by following the steps in KB 89129
3. Query the forms service API to return a list of custom resources referenced in custom forms:
Issue a GET to url https://<vRA-FQDN>/form-service/api/custom/resource-types/ to return all the custom resource types referenced in custom forms
The vRO integration ID is referenced in the "endpointLink" property. In the screenshot below we see the stale integration id of c25cf2bc-e7f9-4a99-a378-8a3a13446c21
4. Document the id of any custom resource types which do not reference the new vRO integration id in their endpointLink properties.
5. Query the affected custom resource types individually by their ID.
Issue a GET to url https://<vRA-FQDN>/form-service/api/custom/resource-types/<ids from step 4>
6. Update the custom resource objects via the forms service API to reference the new Orchestrator integration ID:
For any affected custom resource objects leverage the body returned by the GET request in step 5 and alter the endpoint links to reference the new vRO integration Id documented step 1 then issue a POST to the same forms service API url with the corrected body content:
Update each affected custom resource object individually , you cannot update multiple records in a single POST.
https://<vRA-FQDN>/form-service/api/custom/resource-types/