> For the complete documentation index, see [llms.txt](https://docs.e6data.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/product-documentation/workspaces/update-a-workspace.md).

# Update a Workspace

Workspace updates will be released by e6data to provide new features, improvements, optimization, and bug fixes. 

Workspace updates are necessary under the following circumstances:

* [When Terraform values have been modified and permissions are updated.](#when-terraform-values-have-been-modified-and-permissions-are-updated)
* [Upon version release.](#upon-version-release)

{% hint style="info" %}
Cluster Connectivity will not be automatically enabled after a Workspace update due to the dynamic nature of hostnames/IP addresses.

Cluster connectivity can be restored by enabling it from the e6data console. [Click here for instructions.](broken://pages/wW8LUA5KhwtobWKUkjDU)

All external connectors or internal services connecting to Clusters in an updated Workspace will need to be updated to use the newly generated hostname.
{% endhint %}

## When Terraform values have been modified and permissions are updated

1. Obtain the latest Terraform files from the `e6x-labs/terraform` repo from [Github](https://github.com/e6x-labs/terraform).
2. Navigate to the directory containing the Terraform files. To execute successfully, it is essential to be in the correct directory for the Terraform commands.
3. Configure the `terraform.tfvars` & `provider.tf` files, to match the same details filled out during the initial Workspace installation.
4. Initialize Terraform:

   `terraform init`
5. Generate a Terraform plan and save it to a file (e.g., `e6.plan`):

   `terraform plan -var-file="terraform.tfvars" --out="e6.plan"`

   The `-var-file` flag specifies the input variable file (`terraform.tfvars`) that contains the necessary configuration values for the deployment.
6. Review the generated plan.
7. Apply the changes using the generated plan file:

   `terraform apply "e6.plan"`

   This command applies the changes specified in the plan file (e6.plan) to deploy the e6data workspace in your environment.
8. Make a note of the values returned by the script.
9. Navigate to ***Workspaces*** in the e6data Console
10. Click the name of the ***Workspace*** being updated or click on the kebab menu and select the ***Update*** option from the dropdown.
11. Click ***Update Workspace***
12. Enter the new values returned in step 8.
13. Click ***Update***

{% hint style="info" %}
Please note that this action applies only to workspaces in the <mark style="color:green;">**ACTIVE**</mark> state.
{% endhint %}

## Upon version release

You can update the workspace in two ways:

1. Click on the kebab menu (three dots) for the desired workspace, then proceed to confirm and complete the process.
2. To update the workspace, first click on the desired workspace, then click on the "Update" button. Confirm the update and proceed to complete the process.

{% embed url="<https://www.loom.com/share/f96cd08d35c64243b5f36cedfca1cf6c?sid=51c34dde-69eb-4f24-b082-b303f0bd668e>" %}

{% hint style="info" %}
If the UI isn't updating after a normal refresh, it might be due to the local browser cache. Please close your browser completely and reopen it to resolve the issue.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.e6data.com/product-documentation/workspaces/update-a-workspace.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.