We have a driver that is creating bookings silently. This will use profile instances created beforehand, so the silent booking method is passing the ProfileInstancesIds.
Our problem is that we have a development server, a staging server and a production server. When we provisioned the profile instances on each server, they got a unique GUID, always different. So, every time we finished with a new driver version on the development, we need to push it to the Staging DMA and change the Profile Instances Ids manually. The same needs to be done when we push it on Production.
In order to avoid confusions in the long-term, we were looking to improve this in a way that we don’t have to do the manual fine tuning, every time the driver needs to be published on Staging or Production.
Are there any best pratices that can help on this?
- Can we force a Profile Instance ID on a server?
- On the driver, should we look up for Profile Instances (using the name) and get its ID? (however, renaming a profile instance would break this..)
Hi Bruno,
Both of the suggested options work, but I believe it’s best to use the profile helper and search for the profile by name.
If you add a configuration option in your driver where the expected profile(s) can be defined, then a change of the profile name shouldn’t be an issue, as long as the configuration in the driver is updated when the profile is updated.