When adding a new connection profile, we specify the host for the AM deployment. If the deployment is detected as ForgeOps deployment, when exporting a journey, Frodo tries to export the theme by constructing the IDM URL from the AM URL that is passed. In deployments where IDM is on a different load balanced URL, this request throws 404 error causing frodo to exit the export operation.
It would be beneficial if we can explicitly provide the complete idm URL when adding the profile as shown below so that frodo can fetch resources from each component correctly.
Describe the solution you'd like
When adding a new connection profile, we specify the host for the AM deployment. If the deployment is detected as ForgeOps deployment, when exporting a journey, Frodo tries to export the theme by constructing the IDM URL from the AM URL that is passed. In deployments where IDM is on a different load balanced URL, this request throws 404 error causing frodo to exit the export operation.
It would be beneficial if we can explicitly provide the complete idm URL when adding the profile as shown below so that frodo can fetch resources from each component correctly.
frodo conn add -k https://myam.com/am --idm-host https://myidm.com/openidm XXXX YYYY