For an existing replica set with an auto-scaling group ensures that the auto-scaling group has a minimum size of 1 and waits until an auto-scaling replica is available. Then, all replicas not managed by the auto-scaling group are stopped one by one.
If the replica set does not have an auto-scaling group assigned, no action is taken.
| Webservice Type: | POST |
| Output format: | json |
| Mandatory query parameters: |
regionId, region where to set up the replica set, e.g., eu-west-1
replicaSetName, name of the replica set; used as the hostname to which the domain name is appended, as well as
for the database and RabbitMQ exchange name
privateKeyEncryptionPassphrase, the pass phrase to decrypt the private key for the key specified by the keyName parameter
|
| Optional form parameters: |
keyName, the name of the SSH key to use; must identify an existing SSH key by that name in the region specified
and will be used to log on to existing and new instances using a root ssh connection. If not specified, the
key used to launch an instance will be used for trying to connect to it, and a private key with matching name
for the respective region will be looked up.
timeoutInMilliseconds, timeout in milliseconds to wait for responses from nodes when analyzing the replica sets
existing in the region; if not specified, a typical default for waiting for process responses will be used.
|
| Request method: | POST |
| Example: | curl -X POST -d 'regionId=eu-west-2' -d 'replicaSetName=mynewevent' -d 'keyName=Horst' --data-urlencode 'privateKeyEncryptionPassphrase=HorstsSuperSecretPassword' -H 'Authorization: Bearer RwGK+DV38LKjeuDu+Bx87/3blLJHD7Ff+NCLeud9nRQ=' "https://sapsailing.com/sailinglandscape/api/landscape/usededicatedautoscalingreplicasinsteadofshared"
produces output:
{
"name": "mynewevent",
"version": "build-202112151552"
}
|