Hello Sean, it’s been a while! Hope you’re doing well, sir.
To the topic at hand, storage accounts as a transport are just one (legacy) use case, and I’m looking for specifically some sort of support or options in the nservicebus configuration to provide multiple credentials or connections. From my perspective, it shouldn’t matter what the transport layer is, so long as the destination point can have one set of credentials (shared access key for it) and the error point can have another (different shared access key for it). Based on what you said, it sounds like that option was available in the Storage Queue transport. I’m not sure why it wouldn’t be available (and I suppose subsequently deprecated) across all transports, but that’s neither here nor there.
We can’t help the provisioning scheme, since we can use Terraform to create things exactly the way we want them, and the way we are currently generating access keys is the direction that was provided by our security group. So, we don’t have much wiggle room to alter how we provision (nor does security want us to).
The point I’m trying to clarify is, in nservicebus, regardless of whether you provision a storage account or service bus queue in one subscription or namespace or not, can you provide different connection strings or at least access keys for the various destination centers, regardless of it’s for the actual destination queue, or the error queue? If not, then the software simply doesn’t support our configuration going forward, and we just need to find an alternative. That’s why I’m asking. We’ve been using it to great success so far, but only because it can do the things we need it to be able to do.
If it can’t support separate shared access keys for the multitude of physical endpoints, or within an “endpoint” it can’t support a separate credential set for the destination physical component versus the error physical component, then it can’t support any of the mr.cooper environments going forward for all of our apps / pipelines.
We are transitioning to the new Azure Service Bus transport. Does it support being supplied with shared access keys per destination/error point?
Ahad L. Amdani