Add capability to specify group for Task Server configuration

[gku11ava]

When the task-server configuration is deployed, the configuration targets the task-server for the default group. The group cannot be specified in the app-server config file and the underlying task-server resource from ml-app-deployer does not support the mlGroupName property. This means it is currently not possible to configure task servers in other groups without any changes.

The current workaround is to create a custom task using the ManageClient

[rjrudin]

Thanks, tracking internally via MLE-27162.

To confirm as well - is it sufficient to honor mlGroupName for task servers? That seems like the main omission here . Or would you need the flexibility of specifying task server updates for task servers in different groups?

[hansenmc]

I would expect the group to be inferred from folder structure if under a particular group directory and applied to the querystring parameter, as it does for Servers.

Whether or not you can also control with the mlGroupNamw and whether or not that takes precedence over the group name inferred by the parent folder name - what does it do for Servers? It should be consistent.

[gku11ava]

Inferring the group name from folder structure would be the ideal solution as there is a need to be able to use tasks across multiple groups. mlGroupName also makes sense since it is used to target tasks to a group, but you are then limited to one group.

I think directory structure -> mlGroupName -> Default where directory structure takes the highest priority if it exists.

[rjrudin]

@gku11ava Just a note, we released 6.2.0 but did not address this yet, still have it in our backlog.