We don't necessarily need workflowDomain for non-SWF backends.
We already put other swf-specific parameters in RemoteSwfClientConfig, so this parameter should go there as well.
Users who want to use the same remote region with different domains should simply define different "endpoint IDs" for each domain.
It looks like this parameter isn't being honored anyway; the underlying RemoteWorkflowExecutorImpl actually pulls it from FluxCapacitorConfig. It's probably worth not using FluxCapacitorConfig there at all, and get both the swf domain and AutomaticallYTagExecutionsWithTaskList from RemoteSwfClientConfig.
We don't necessarily need workflowDomain for non-SWF backends.
We already put other swf-specific parameters in RemoteSwfClientConfig, so this parameter should go there as well.
Users who want to use the same remote region with different domains should simply define different "endpoint IDs" for each domain.
It looks like this parameter isn't being honored anyway; the underlying RemoteWorkflowExecutorImpl actually pulls it from FluxCapacitorConfig. It's probably worth not using FluxCapacitorConfig there at all, and get both the swf domain and AutomaticallYTagExecutionsWithTaskList from RemoteSwfClientConfig.