Open APIs

Hello experts,

The TMF641 specification uses the specification identifier (serviceSpecification.id) to refer to unique specification in the catalog.
And it is all great until we add environment management and the rest of DevOps processes on top of it.

I wasn't able to find a reference in the specs either the serviceSpecification.id is supposed to be environment-agnostic or not. Clearly, I'd like it to be env-agnostic to avoid additional configuration activities due to env changes. But I wasn't able to find anything in the specs to support this claim.

Cheers,
Alexander

------------------------------
Alexander Morozov
Vlocity
------------------------------

I would suggest that this is an implementation decision. You could (for instance) use GUID generation for your IDs, guaranteeing complete uniqueness everywhere. If GUIDs are too long for your storage, you could devise some shorter ID format that concatenates environment id and some sort of timestamp + random number, giving a close approximation of uniqueness.
This is relevant for all catalogs, not just service catalog.
Hope it helps

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------