From 03f2b564ccbb9e83f186b432dd2d2cec2d21ff3e Mon Sep 17 00:00:00 2001 From: Vj-L <102945356+Vj-L@users.noreply.github.com> Date: Thu, 22 Dec 2022 15:19:26 +0530 Subject: [PATCH] Updated the docs for upgrade bare-metal (#9485) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Updated the docs for upgrade bare-metal * Updated the docs for upgrade bare-metal * Updated as per the comments Co-authored-by: “Vijay” <“vijay.l@deuexsolutions.com”> --- openmetadata-docs/content/deployment/upgrade/bare-metal.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/openmetadata-docs/content/deployment/upgrade/bare-metal.md b/openmetadata-docs/content/deployment/upgrade/bare-metal.md index 11fe60c2ae6..da3f8c447f9 100644 --- a/openmetadata-docs/content/deployment/upgrade/bare-metal.md +++ b/openmetadata-docs/content/deployment/upgrade/bare-metal.md @@ -19,13 +19,14 @@ This guide assumes that you have an OpenMetadata deployment that you installed a It is adviced to go through [openmetadata release notes](/deployment/upgrade/versions/012-to-013) before starting the upgrade process. + ### Backup 0.12.3 data 1. Make sure your instance is connected to the Database server 2. Create a virtual environment to install an upgraded `metadata` version to run the backup command: 1. `python -m venv venv` 2. `source venv/bin/activate` - 3. `PIP_USER=false pip install openmetadata-ingestion~=0.13.1` + 3. `pip install openmetadata-ingestion~=0.13.1.0` 3. Validate the installed `metadata` version with `python -m metadata --version`, which should tell us that we are indeed at 0.13.1. Notice the `python -m metadata` vs. `metadata`. 4. Run the backup using the updated `metadata` CLI: @@ -75,7 +76,9 @@ For example, to navigate into the directory created by issuing the tar command a command. ```commandline -cd openmetadata-0.13.0 + +cd openmetadata-0.13.1 + ``` ### 4. Stop the OpenMetadata server