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

Jump to bottom

Tweak to documentation explaining caveats with dataset_size_in_gb attribute #566

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Tweak to documentation explaining caveats with dataset_size_in_gb attribute #566

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 8 additions & 1 deletion docs/resources/rediscloud_active_active_subscription_database.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,5 +179,12 @@ $ terraform import rediscloud_active_active_subscription_database.database-resou

Note: Due to constraints in the Redis Cloud API, the import process will not import global attributes or override region attributes. If you wish to use these attributes in your Terraform configuration, you will need to manually add them to your Terraform configuration and run `terraform apply` to update the database.

Additionally, the `memory_limit_in_gb` cannot be set during imports as it is deprecated. If you need to set the `memory_limit_in_gb` attribute, you will need to create a new database resource. It is recommended to use the `dataset_size_in_gb` attribute instead.
Additionally, the `memory_limit_in_gb` cannot be set during imports as it is deprecated. If you need to set the `memory_limit_in_gb` attribute, you will need to create a new database resource. It is recommended to use the `dataset_size_in_gb` attribute instead since imports are supported.

To update an existing configuration for a database which uses the `memory_limit_in_gb` field to use `dataset_size_in_gb`, you need to remove it from the state and import the resource again. e.g.

```
$ terraform state rm rediscloud_active_active_subscription_database.database-resource
(Update the configuration to use `dataset_size_in_gb` instead of `memory_limit_in_gb`)
$ terraform import rediscloud_active_active_subscription_database.database-resource 123456/12345678
```
10 changes: 9 additions & 1 deletion docs/resources/rediscloud_subscription_database.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -189,4 +189,12 @@ The `response` block `latest_import_status` contains:
$ terraform import rediscloud_subscription_database.database-resource 123456/12345678
```

Note: Due to constraints in the Redis Cloud API, the `memory_limit_in_gb` cannot be set during imports as it is deprecated. If you need to set the `memory_limit_in_gb` attribute, you will need to create a new database resource. It is recommended to use the `dataset_size_in_gb` attribute instead.
Note: Due to constraints in the Redis Cloud API, the `memory_limit_in_gb` cannot be set during imports as it is deprecated. If you need to set the `memory_limit_in_gb` attribute, you will need to create a new database resource. It is recommended to use the `dataset_size_in_gb` attribute instead since imports are supported.

To update an existing configuration for a database which uses the `memory_limit_in_gb` field to use `dataset_size_in_gb`, you need to remove it from the state and import the resource again. e.g.

```
$ terraform state rm rediscloud_subscription_database.database-resource
(Update the configuration to use `dataset_size_in_gb` instead of `memory_limit_in_gb`)
$ terraform import rediscloud_subscription_database.database-resource 123456/12345678
```
Loading