Migrate planedit
Migrates the configuration of the Elasticsearch cluster to a different template.
Requestedit
POST /api/v1/clusters/elasticsearch/{cluster_id}/plan/_migrate
Path parametersedit
| Name | Type | Required | Description |
|---|---|---|---|
|
|
Y |
The Elasticsearch cluster identifier. |
Query parametersedit
| Name | Type | Required | Description |
|---|---|---|---|
|
|
Y |
The ID of the deployment template to migrate to |
|
|
N |
When true, validates the cluster definition, but does not perform the update |
Responsesedit
-
200 -
(
ClusterPlanMigrationResponse) The current cluster plan migrated to the specified deployment template. -
202 -
(
ClusterPlanMigrationResponse) The plan definition was valid and the updated plan is in progress -
400 -
(
BasicFailedReply) Migrating to the specified template would lead to an invalid or unsupported cluster definition. (code:clusters.cluster_invalid_plan) -
404 -
(
BasicFailedReply) The cluster specified by {cluster_id} cannot be found. (code:clusters.cluster_not_found) -
412 -
(
BasicFailedReply) There is not currently applied plan - eg the cluster has not finished provisioning, or the provisioning failed. (code:clusters.cluster_plan_state_error) -
449 -
(
BasicFailedReply) Elevated permissions are required. (code:root.unauthorized.rbac.elevated_permissions_required)
To perform this operation, you must be authenticated by means of one of the following methods: apiKey, basicAuth.
Request exampleedit
curl -XPOST {{hostname}}/api/v1/clusters/elasticsearch/{cluster_id}/plan/_migrate \
-u $CLOUD_USER:$CLOUD_KEY