Register Azure messaging clients with synchronous secret retrieval
Microsoft provides some easy extensions to register a
EventHubsProducerClient to your application services. The problem is that when you do not use managed identity, you have to provide the authentication access signature yourself (and if this uses the application configuration, we know it is incorrect). v1.4 includes some minor but powerful changes regarding Azure messaging client registrations. This means that the clients are using the Arcus secret store for their access signatures.
Only a secret name is required when registering your Azure messaging client, easily delegating the complexity of secret management to the secret store:
This is also a great example of how Arcus and Microsoft work together. In the past, both had their own way of registering clients, but with changes like these, we bridge the gap and strengthen each other.
For more information about this feature, see our dedicated feature documentation for Service Bus and EventHubs.
This is a very practical feature that will hopefully help a lot of applications handle their service interactions. For more information about this feature, see our dedicated feature documentation.
Arcus Messaging v1.4 is a big step towards seamless incorporation with Microsoft technology. Our abstracted way of messaging has a real beneficial value and if we can reuse existing Microsoft technology, we only strengthen the bond.
Have a look at our release notes and official documentation for more information on this new release.
If you have any questions, remarks, comments, or just want to discuss something with us: feel free to contact the Arcus team at Codit.
Thanks for reading!
The Arcus team
Subscribe to our RSS feed