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
Describe the bug
I am using current Terraform IaC code provided on https://github.com/kasmtech/terraform/blob/develop/aws/multi_region/README.md. It creates the database container and other resources on applying the code on AWS. The issues is, when I tried changing AMI for db instance, it seems deleting the root volume too. So all the configuration I created through admin portal are getting vanished. Shouldn't the db volume retained while upgrade and attach to the new replacement instance?
Describe the bug
I am using current Terraform IaC code provided on https://github.com/kasmtech/terraform/blob/develop/aws/multi_region/README.md. It creates the database container and other resources on applying the code on AWS. The issues is, when I tried changing AMI for db instance, it seems deleting the root volume too. So all the configuration I created through admin portal are getting vanished. Shouldn't the db volume retained while upgrade and attach to the new replacement instance?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
DB volume should be retained and attached to the new replaced instance so configuration and all the data will be there.
Workspaces Version
e.g Version 1.16.1
Workspaces Installation Method
e.g Multi-region, Multi-Server, terraform
The text was updated successfully, but these errors were encountered: