From ff8867c7b6066e638b251c0f41e8aa343d23aa14 Mon Sep 17 00:00:00 2001
From: Rikin Kachhia <54616969+rikinsk@users.noreply.github.com>
Date: Wed, 10 Mar 2021 02:57:26 +0530
Subject: [PATCH] docs: add workaround to change region for cloud v2.0 projects

GitOrigin-RevId: deb7db4d70793b3ca3b7df222909ca1c2db8003d
---
 docs/graphql/cloud/projects/regions.rst | 38 +++++++++++++++++++++++--
 1 file changed, 36 insertions(+), 2 deletions(-)

diff --git a/docs/graphql/cloud/projects/regions.rst b/docs/graphql/cloud/projects/regions.rst
index 3d6772e06fe..b55153e1886 100644
--- a/docs/graphql/cloud/projects/regions.rst
+++ b/docs/graphql/cloud/projects/regions.rst
@@ -34,6 +34,7 @@ Go the the project details by clicking on the settings icon on your project card
 
 .. thumbnail:: /img/graphql/cloud/getting-started/project-manage.png
    :alt: select regions while project creation
+   :width: 900px
 
 The ``Region`` field displays the project's current region of deployment. For switching the region, click on the edit icon in the ``Region`` field.
 
@@ -50,7 +51,40 @@ There might be a short downtime while your project is being moved to a different
 .. thumbnail:: /img/graphql/cloud/projects/region-edit-hasura-cloud-ip.png
    :alt: change region confirm box
 
+.. note::
 
-.. admonition:: Note
+   Support for deploying a project in multiple regions is coming soon.
 
-    Support for deploying a project in multiple regions is coming soon.
\ No newline at end of file
+.. _project_regions_v2_limitation:
+
+.. admonition:: Temporary limitation for v2.0 projects
+
+   Due to an underlying architecture change, it is currently not possible to change regions of already created ``v2.0`` projects.
+   **Support for this will be added in the very near future.**
+
+   In the meanwhile, as a workaround, you can "move" your project to a new region by creating a new Hasura project
+   in the region you wish and connect it with your database with the same Hasura metadata as in the previous project.
+
+   **Step 1: Export metadata from existing project**
+
+   See :ref:`exporting metadata <exporting_metadata>` to get a copy of the current Hasura metadata
+   on your project.
+
+   Do ensure no further changes are made to the Hasura metadata post this.
+
+   **Step 2: Create a v2.0 Cloud project in your region**
+
+   See ``Step 1`` of :ref:`creating projects <create_project>` to create a new Hasura Cloud ``v2.0``
+   project in the region you wish.
+
+   **Step 3: Connect your database with the same name to the new project**
+
+   See ``Step 2`` of :ref:`creating projects <create_project>` to connect your existing database to
+   the new project. Please ensure you set the same database name as in the current project.
+
+   **Step 4: Apply the exported metadata to the new project**
+
+   See :ref:`applying metadata <applying_metadata>` to apply the earlier exported metadata to the new
+   project.
+
+   Your GraphQL API should now be regenerated as in the earlier project.