We are moving much of the broker configuration functionality from the microservice to the Registry Service. This has several implications.
Brokers
We now only support the following functionality on the Client/Service side:
Users will no longer provide broker credentials themselves, and will no longer do any kind of exchange/queue configuration on the microservice side (this will now all be handled by the registry service). The credentials users will receive from the registry service will only allow them to publish/subscribe to a narrow range of topics.
Data plane
The credentials for MINIO (and others) will also be provided by the registry service, however we will still support the same GET/PUT operations as before.
Config
One of the most user-friendly changes, this simplifies the configurations people need to keep track of.
The IntersectServiceConfig will be simplified to:
class IntersectServiceConfig(BaseModel):
registry_service_url: str
api_key: str
service_name: str
The IntersectClientConfig will be simplified to:
class IntersectClientConfig(BaseModel):
registry_service_url: str
api_key: str
Users use a centralized authentication service to gain access to the main Intersect Registry Service. From there, they can:
- see the common Client API key that they may use in the ClientConfig
- reserve a Service namespace, take both it and the generated API key, and use both for the Service config
The Registry Service will now send back the old Intersect configs, plus some additional options. This is all managed internally and does not need to be dealt with by a user.
Misc
We are moving much of the broker configuration functionality from the microservice to the Registry Service. This has several implications.
Brokers
We now only support the following functionality on the Client/Service side:
Users will no longer provide broker credentials themselves, and will no longer do any kind of exchange/queue configuration on the microservice side (this will now all be handled by the registry service). The credentials users will receive from the registry service will only allow them to publish/subscribe to a narrow range of topics.
Data plane
The credentials for MINIO (and others) will also be provided by the registry service, however we will still support the same GET/PUT operations as before.
Config
One of the most user-friendly changes, this simplifies the configurations people need to keep track of.
The IntersectServiceConfig will be simplified to:
The IntersectClientConfig will be simplified to:
Users use a centralized authentication service to gain access to the main Intersect Registry Service. From there, they can:
The Registry Service will now send back the old Intersect configs, plus some additional options. This is all managed internally and does not need to be dealt with by a user.
Misc
campaign_idin the messages (see "API Token Correlation ID" in For service - store a correlation ID + token ID for API token sent to User registry-service#2)