Topology components and relations created via otel mappings are required to have an identifier. We use a urn scheme where the identifiers start with urn:<scope/stackpack>:<custom-from-here>:<encoding>:<name>. However we never enforce it.
In releases 2.8.x and 2.9.x we temporarily enforced urn: prefix on the api, which caused problems at NN when they upgraded (components wouldn’t load). In 2.10.x we (accidentally? and) luckily reverted this.
Seems we now have the opportunity to at least enforce the format is a urn when created from otel mappings.
STAC-25562
Topology components and relations created via otel mappings are required to have an identifier. We use a urn scheme where the identifiers start with urn:<scope/stackpack>:<custom-from-here>:<encoding>:<name>. However we never enforce it.
In releases 2.8.x and 2.9.x we temporarily enforced urn: prefix on the api, which caused problems at NN when they upgraded (components wouldn’t load). In 2.10.x we (accidentally? and) luckily reverted this.
Seems we now have the opportunity to at least enforce the format is a urn when created from otel mappings.