Updating Hasura Cloud v1.3 projects to Hasura v2.0¶

Introduction¶

Hasura Cloud now creates new projects with Hasura v2.0 by default. Due to some behaviour and underlying architectural changes in v2.0, existing projects have not been auto-updated to v2.0. You can update your older v1.3 projects to v2.0 by following this guide.

(You can find the older guide to do this process manually here)

What has changed?¶

Check the core updating to v2.0 guide and the release notes to see what new concepts, features and behaviour changes have been introduced in Hasura v2.0.

Note that Hasura v2 Cloud projects’ metadata is now stored in metadata DBs managed by Hasura Cloud. Hence the new HASURA_GRAPHQL_METADATA_DATABASE_URL env var is not configurable on Hasura Cloud and is managed by Hasura Cloud itself.

See the section on Hasura v1 and Hasura v2 compatibility to use a Hasura v2 Cloud project like a Hasura v1 Cloud project.

Estimated time needed for update¶

Depending on the size of your project the update process should typically take around 5-10 minutes to be completed.

Project availability during update¶

During the update process Hasura Cloud will need to place your project in a “Maintenance mode” till the process is complete.

When Cloud maintenance mode is enabled, all Hasura Cloud project actions such as updating env vars, transferring ownership, etc. will be disabled.

When Server maintenance mode is enabled, all actions updating the project metadata such as tracking tables, adding relationships, etc. will be disabled.

Hence it is recommended to update your project at a time convenient to all project collaborators.

Apart from the brief moments needed to enable/disable the server maintenance mode, your GraphQL API will continue to function during this period.

Post-update steps¶

• As with most major updates, we would recommend you to monitor and ensure all functionalities of your project are working as expected post the update and the update did not cause any unexpected changes. Do get in touch with us in case you notice anything unexpected.
• You can choose to unset the HASURA_GRAPHQL_V1_BOOLEAN_NULL_COLLAPSE env var that was added to your project during the update to preserve a v1.3 behaviour that was modified in v2.0. See details. We recommend moving to the new behaviour by unsetting the env var after verifying your project is not impacted by the change.
• Check the Post update steps section of the core updating to v2.0 guide for other changes you should make post your project update.

Update process¶

To start the update, you should see a button called Update next to your project on the Project list page as shown below:

Clicking on this button will trigger an update job that will perform a few tasks to update your current v1.3 project to v2.0.

Refer to the following task wise breakdown of the update job to understand what the job will be doing and to check your project end state in case of any failures.

Do reach out to support if you observe any issues with the update process or run into any other problems post the v2.0 update.