Add support for `Enable-SupervisorCluster` to name a supervisor cluster

[benhtodd]

Code of Conduct

• [X] I have read and agree to the project's Code of Conduct.
• [ ] Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• [ ] Do not leave "+1" or other comments that do not add relevant information or questions.
• [ ] If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Would like Enable-SupervisorCluster to be able to name the Supervisor cluster with a custom name. Currently it names the supervisor from the parameter -Cluster which is clearly documented as The name of the vSphere cluster. There is a parameter -mastetDNSName which is documented as "The master DNS name." Which I am not so sure I know what it means. I tried it for my purposes to no avail.

Use Case(s)

Is it a must the Supervisor Cluster is to be named the same as the vsphere cluster?

Potential Configuration

Parameter called -supervisorName....?

References

No response

[tenthirtyam]

Looks like this is simply based on the current logic of the function that includes:

Cluster = (Get-Cluster -Name $cluster)

For example:

param (
    [Parameter (Mandatory = $true)] [ValidateNotNullOrEmpty()] [String]$cluster,
    [Parameter (Mandatory = $false)] [ValidateNotNullOrEmpty()] [String]$supervisorName
)

# other...

if ($inputParameterValidation -eq $true) {
    $internalWMClusterInput = @{
        # other...
        Cluster = $supervisorName -or (Get-Cluster -Name $cluster)
        # other...
    }
}

# other...

This way, if $supervisorName is provided, it will be used directly; otherwise, it will get the cluster by the name $cluster.

[benhtodd]

@tenthirtyam - Not able to pass supervisorName ?

[tenthirtyam]

My comment above is a possible fix for the function.