Unable to attach Morpheus Workflow to Morpheus Network Domain via API v7.0.9

[slothkong]

This  issue seems to currenlty affects the Morpheus API v7.0.9, for self-hosted  installations (on-premise) .

Expected Behavior

As per the officail documentation [1], it should be possible to create a Morpheus Worflow Domain via the API using the following curl command:

curl \
	--insecure \
	--request POST \
	--url 'https://morpheus.example.com/api/networks/domains' \
	--header 'authorization: Bearer <redacted>' \
	--header 'accept: application/json' \
	--header 'content-type: application/json' \
	--data '
{
  "networkDomain": {
    "publicZone": false,
    "domainController": false,
    "name": "internal.example.com",
    "taskSetId": 260,
    "active": true
  }
}'

 where TaskSetId is the ID (int64) of an existing Morpheus Workflow.
The response should be 200 OK.
Any instance provisioned under the internal.example.com Morpheus Network Domain should trigger the Morpheus Workflow in question.

Observed Behavior

The Morpheus Network Domain is created (200 Ok).
However, the desired Morpheus Workflow does not trigger for any machine provisied within the Morpheus Network Domain.
Furthermore, from within the UI of the Morpheus Appliance, the Morpheus Network Domain shows as if no Morpheus Workflow had been configured.
Getting the configuration of the Morpheus Network Domain via API does not clarify whether the creation truely succeeded, as TaskSetId is not part of the response schema.

Updating the Morpheus Network Domain via the UI achieves the desired behaviour of Workflow triggering upon instance provisioning. However, having to manually edit the Network Domain via UI defeats the purpose.

[1] https://apidocs.morpheusdata.com/v7.0.9/reference/createnetworkdomain