Devops and Marketplace - What happens to Object API ? How to keep the same APIs for different deployment?

I have an Ontology, with a Developer Application/osdk on top.
I want to perform API calls towards this Ontology.

The project, including its objects and developer console application/osdk were packaged in Marketplace and redeployed in a second Project.

I want to have an external system that can plug to the ontology of Project 1 or Project 2 in a smooth way.

Questions:

  1. What happens to the APIs name generated on the Objects Types when they are marketplaced and deployed a second time (within the same Ontology) ? What stays the same and what changes ?
  2. How can I point to one vs the other from my external application ?

For 1. to my understanding, if there is no conflict, the API will stay the same (which means that deploying the object in a different ontology will yield the same API names, but in the same ontology will generate different API names, for example, to avoid conflicts) - Is that correct ?

The underlying use case and goal is to have 2 set of Objects (dev and prod) and be able to switch from one to the other without (any ?) code change from downstream application.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.