You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This updated configuration will trigger a Terraform update plan. However, the underlying cluster will not face any changes after the `apply` command, as both configurations represent a sharded cluster composed of two shards.
89
89
90
-
Note: The first time `terraform apply` command is run **after** updating the configuration, you may receive a `500 Internal Server Error (Error code: "SERVICE_UNAVAILABLE")` error. This is a known temporary issue. If you encounter this, please re-run `terraform apply` and this time the update should succeed.
This updated configuration triggers a Terraform update plan. However, the underlying cluster will not face any changes after the `apply` command, as both configurations represent a geo sharded cluster with two zones and two shards in each one.
199
197
200
-
Note: The first time `terraform apply` command is run **after** updating the configuration, you may receive a `500 Internal Server Error (Error code: "SERVICE_UNAVAILABLE")` error. This is a known temporary issue. If you encounter this, please re-run `terraform apply` and this time the update should succeed.
Note: The first time `terraform apply` command is run **after** updating the configuration, you may receive a `500 Internal Server Error (Error code: "SERVICE_UNAVAILABLE")` error. This is a known temporary issue. If you encounter this, please re-run `terraform apply` and this time the update should succeed.
Copy file name to clipboardExpand all lines: docs/resources/advanced_cluster (preview provider 2.0.0).md
-1
Original file line number
Diff line number
Diff line change
@@ -935,7 +935,6 @@ See detailed information for arguments and attributes: [MongoDB API Advanced Clu
935
935
936
936
~> **IMPORTANT:**
937
937
<br> • When a cluster is imported, the resulting schema structure will always return the new schema including `replication_specs` per independent shards of the cluster.
938
-
<br> • Note: The first time `terraform apply` command is run **after** updating the configuration of an imported cluster, you may receive a `500 Internal Server Error (Error code: "SERVICE_UNAVAILABLE")` error. This is a known temporary issue. If you encounter this, please re-run `terraform apply` and this time the update should succeed.
Copy file name to clipboardExpand all lines: docs/resources/advanced_cluster.md
-1
Original file line number
Diff line number
Diff line change
@@ -767,7 +767,6 @@ See detailed information for arguments and attributes: [MongoDB API Advanced Clu
767
767
768
768
~> **IMPORTANT:**
769
769
<br> • When a cluster is imported, the resulting schema structure will always return the new schema including `replication_specs` per independent shards of the cluster.
770
-
<br> • Note: The first time `terraform apply` command is run **after** updating the configuration of an imported cluster, you may receive a `500 Internal Server Error (Error code: "SERVICE_UNAVAILABLE")` error. This is a known temporary issue. If you encounter this, please re-run `terraform apply` and this time the update should succeed.
// retrying get operation because for migration test it can be the first time new API is called for a cluster so API responds with temporary error as it transition to enabling ISS FF
0 commit comments