The AccountRoutingSettings.AddEndpoint implements too many concerns

[boblangley]

Describe the suggested improvement

The AddEndpoint command is used to both provide routing details for endpoints on other accounts for commands (1st concern) and also inform subscriber endpoints which account to use (2nd concern) as well as configuring the subscription table name used in the other account (3rd concern).

Is your improvement related to a problem? Please describe.

Describe the suggested solution

AddEndpoint should be changed to just handle the concern of routing commands to endpoints on other accounts.
One or more methods should be added to configure publisher details:
A method should be added to register message types to be subscribed from other accounts, and should not require the publisher endpoint name.
Either an optional parameter on the previous method or a new method should be added to configure the subscription table name used in the other account.

Describe alternatives you've considered

Keeping things the way they are.

Additional Context

No response

[mauroservienti]

@boblangley, we looked for what is mentioned in this issue, but were unable to find the code about the three concerns you are referring to. We think we've found the code, but there is only one concern addressed there, the latter in your description.

NServiceBus.AzureStorageQueues/src/Transport/Config/Extensions/AccountInfo.cs

Lines 44 to 50 in fc181fd

	public AccountInfo AddEndpoint(string endpointName, IEnumerable<Type> publishedEvents = null, string subscriptionTableName = null)
	{
	var tableName = string.IsNullOrEmpty(subscriptionTableName) ? SubscriptionSettings.DefaultSubscriptionTableName : subscriptionTableName;
	PublishedEventsByEndpoint.Add(endpointName, (publishedEvents ?? Enumerable.Empty<Type>(), tableName));
	return this;
	}

Can you clarify or close this issue?