In order to make valid requests to the provisioning system to set the number of nodes in a cluster, clients need the ability to determine what the minimum and maximum number of nodes allowed for the cluster are (otherwise a node request is rejected).
Currently the /api/org_num_nodes/{organization} api returns an error if the cluster is not deployed; but it needs to return the min and max even when the cluster is not deployed so a client can successfully deploy the cluster.
In order to make valid requests to the provisioning system to set the number of nodes in a cluster, clients need the ability to determine what the minimum and maximum number of nodes allowed for the cluster are (otherwise a node request is rejected).
Currently the /api/org_num_nodes/{organization} api returns an error if the cluster is not deployed; but it needs to return the min and max even when the cluster is not deployed so a client can successfully deploy the cluster.