Add option for cluster name in configure_replication_private

[KowMangler]

Is your feature request related to a problem? Please describe.

I can't specify a cluster name in configure_replication_private and that prevents me from making the function itself idempotent since the value returned from the "GET" method returns whatever the current delegation is for the remote/central communication pairing.

i.e.

• Cluster consists of 11 nodes: 10.10.10.10 - 10.10.10.20

• Add replication target 10.10.10.10 on remote edge node

• Do GET method to retrieve targetClusterAddress field returns 10.10.10.12 value since 12 had the least amount of replication jobs at the time. Could be 10.10.10.15 tomorrow.

Describe the solution you'd like

Allow me to specify the targetClusterName in the function (even though in the API call it would be unused) in order to measure whether or not the call would effect a change.

EDIT: (Otherwise the call returns an error.) <- statement is untrue. all that happens is the cluster returns the response that the replication target has been created.

Describe alternatives you've considered

• GET method then lookup targetClusterAddress in a table to see if it is a part of the existing cluster target.

• Create an RFE for the Rubrik API itself to return the possible cluster IP values as well as the currently paired node.

Additional context

Add any other context or screenshots about the feature request here.

[drew-russell]

@KowMangler will dig into this later today

[KowMangler]

Correcting the original statement that an error occurs. No error occurs, just the call returns 200 and the replication target is "set" even though it was already set. This is inconsistent with a majority of the API calls where via the SDK where if the configuration is identical nothing is set.

What I'm trying to do is get more ansible modules built. I can move logic to the ansible modules for this particular module but I want to see what the opinion of maintainers are.

[KowMangler]

The real issue is how to handle the validation check. I can think of two options:

• Create a connection to the replication target cluster using the provided credentials and retrieve the cluster name to determine if the cluster has already been added as a replication target. I think this is preferable but has caveats in that BOTH node being configured and cluster used as target must be accessible. This may not be immediately possible in some high-security environments which is probably acceptable

• Force the user to provide the cluster name and compare the cluster name to the cluster name in the get method (normalized to upper or lowercase)

[KowMangler]

opted for first option creating the ansible module. can change it depending on what comes of this issue.