The changes made to the vertx consul client for the extended meta data changes
Motivation:
If there was an external service that needed to register more than 64 meta data entries (for routing i.e. IPv6 prefix ranges), the NFRA would simply fail to register that service instance.
Solution
If the NFRA detects that more than 64 meta data entries are needed, then all meta data is stored in a KV entry, rather than the service instance meta data storage.
The service instance meta data storage has a single entry, which points to the KV store entry key, holding the actual meta data.
The changes made to the vertx consul client for the extended meta data changes
Motivation:
If there was an external service that needed to register more than 64 meta data entries (for routing i.e. IPv6 prefix ranges), the NFRA would simply fail to register that service instance.
Solution If the NFRA detects that more than 64 meta data entries are needed, then all meta data is stored in a KV entry, rather than the service instance meta data storage. The service instance meta data storage has a single entry, which points to the KV store entry key, holding the actual meta data.