Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: Updatesmongodbatlas_advanced_cluster ISS migration guide & resource doc with expected 500 error on update #2525

Merged
merged 3 commits into from
Aug 26, 2024
Merged

doc: Updatesmongodbatlas_advanced_cluster ISS migration guide & resource doc with expected 500 error on update #2525

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2f10a93
update docs about temporary error
maastha Aug 23, 2024
6660559
update upgrade guide
maastha Aug 26, 2024
407aec9
update changelog entries
maastha Aug 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/guides/advanced-cluster-new-sharding-schema.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,8 @@ resource "mongodbatlas_advanced_cluster" "test" {

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.

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.

<a id="migration-geosharded"></a>
### Migrate advanced_cluster type `GEOSHARDED`

Expand Down Expand Up @@ -192,6 +194,8 @@ resource "mongodbatlas_advanced_cluster" "test" {

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.

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.

<a id="migration-replicaset"></a>
### Migrate advanced_cluster type `REPLICASET`

Expand Down Expand Up @@ -274,6 +278,8 @@ resource "mongodbatlas_advanced_cluster" "test" {
}
```

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.

<a id="use-iss"></a>
### Use Independent Shard Scaling

Expand Down
1 change: 1 addition & 0 deletions docs/resources/advanced_cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -693,3 +693,4 @@ See detailed information for arguments and attributes: [MongoDB API Advanced Clu

~> **IMPORTANT:**
<br> &#8226; When a cluster is imported, the resulting schema structure will always return the new schema including `replication_specs` per independent shards of the cluster.
<br> &#8226; 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.
Loading