You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to create some kind of functionality which extracts the Tenant information from Hono in order to automatically provision messaging resources in EnMasse.
Basically taking newly created tenants (or recently dropped ones) to requests addresses from EnMasse instead of manually executing a curl command.
The text was updated successfully, but these errors were encountered:
Would that be plugged into the creation of a tenant then?
Or are you more thinking of a making all tenant information accessible from EnMasse, so it could synchronize at any time?
In the latter case, I would have the concern that in true multi tenant setups IMHO usually there is no "super user" that can access all tenants, but only single tenant users that can access exactly the tenant that they were created for.
Up until now I haven't any specific plans other than getting rid of manual provisioning.
The way the service broker works (at least my basic understanding of it) would be that some component (e.g. the Hono component having all the tenant informations) would publish a request for new resources. EnMasse would pick this up (or would get informed) and provision the new resources.
If there is a "super user" it would be OpenShift/Kubernetes probably with service accounts.
I would like to make sure, though, that we do not introduce a direct dependency on an enMasse component in Hono. An elegant way to solve this might be to publish corresponding events from within the Tenant service which could be processed by enMasse in order to manage the resources ...
I would like to create some kind of functionality which extracts the Tenant information from Hono in order to automatically provision messaging resources in EnMasse.
Basically taking newly created tenants (or recently dropped ones) to requests addresses from EnMasse instead of manually executing a
curl
command.The text was updated successfully, but these errors were encountered: