From bb55210078432c56ffe72766918d4c5c9f07ac96 Mon Sep 17 00:00:00 2001 From: open-metadata Date: Fri, 13 Dec 2024 13:21:25 +0000 Subject: [PATCH] See https://github.com/open-metadata/OpenMetadata/commit/cab9245b4dab76201a3d363c27728c0afe2428ea from refs/heads/main --- .../openmetadata-ops.md | 54 +++++++++++++++++++ .../openmetadata-server.md | 4 ++ .../openmetadata-ops.md | 54 +++++++++++++++++++ .../openmetadata-server.md | 4 ++ .../openmetadata-ops.md | 54 +++++++++++++++++++ .../openmetadata-server.md | 4 ++ 6 files changed, 174 insertions(+) create mode 100644 content/v1.5.x/developers/contribute/build-code-and-run-tests/openmetadata-ops.md create mode 100644 content/v1.6.x/developers/contribute/build-code-and-run-tests/openmetadata-ops.md create mode 100644 content/v1.7.x-SNAPSHOT/developers/contribute/build-code-and-run-tests/openmetadata-ops.md diff --git a/content/v1.5.x/developers/contribute/build-code-and-run-tests/openmetadata-ops.md b/content/v1.5.x/developers/contribute/build-code-and-run-tests/openmetadata-ops.md new file mode 100644 index 00000000..6366607f --- /dev/null +++ b/content/v1.5.x/developers/contribute/build-code-and-run-tests/openmetadata-ops.md @@ -0,0 +1,54 @@ +--- +title: Understanding openmetadata-ops.sh file +slug: /developers/contribute/build-code-and-run-tests/openmetadata-ops +--- + +# Understanding openmetadata-ops.sh file +Learn how to run the OpenMetadata Ops in development mode by using commands. + +#### Key Commands: +How to run the `openmetadata-ops.sh` file. +```shell +sh bootstrap/openmetadata-ops.sh [OPTIONS] [COMMANDS] +``` + +#### Options: + 1. -c, --config= + 2. -d, --debug + 3. -h, --help Show this help message and exit. + 4. -V, --version Print version information and exit. + +**Example:** +```shell +sh bootstrap/openmetadata-ops.sh --help +``` + +#### Commands: + 1. **migrate** Migrates the OpenMetadata database schema and search index mappings. + + 2. **reindex** Re Indexes data into search engine from command line. + + 3. **repair** Repairs the DATABASE_CHANGE_LOG table which is used to trackall the migrations on the target database. This involves removing entries for the failed migrations and updatethe checksum of migrations already applied on the target database. + + 4. **validate** Checks if the all the migrations haven been applied on the target database. + + 5. **drop-create** Deletes any tables in configured database and creates a new tables based on current version of OpenMetadata. This command also re-creates the search indexes. + + 6. **deploy-pipelines** Deploy all the service pipelines. + + 7. **analyze-tables** Migrate secrets from DB to the configured Secrets Manager. Note that this does not support migrating between external Secrets Managers. + + 8. **changelog** Prints the change log of database migration. + + 9. **check-connection** Checks if a connection can be successfully obtained for the target database + + 10. **info** Shows the list of migrations applied and the pending migration waiting to be applied on the target database + + 11. **migrate-secrets** Migrate secrets from DB to the configured Secrets Manager. Note that this does not support migrating between external Secrets Managers + + 12. **syncEmailFromEnv** Sync the email configuration from environment variables + +**Example:** +```shell +sh bootstrap/openmetadata-ops.sh migration +``` \ No newline at end of file diff --git a/content/v1.5.x/developers/contribute/build-code-and-run-tests/openmetadata-server.md b/content/v1.5.x/developers/contribute/build-code-and-run-tests/openmetadata-server.md index ac3fbeb5..97e7ecf4 100644 --- a/content/v1.5.x/developers/contribute/build-code-and-run-tests/openmetadata-server.md +++ b/content/v1.5.x/developers/contribute/build-code-and-run-tests/openmetadata-server.md @@ -50,6 +50,10 @@ Extract the distribution tar.gz file created on the previous step and run the fo cd open-metadata- sh bootstrap/openmetadata-ops.sh drop-create ``` +{%note%} +Why Needed: The script simplifies the setup and execution of OpenMetadata by handling Java dependencies, configurations, and environment variables automatically. +{%/note%} +**Note** To understand more about openmetadata-ops.sh file click [here](/developers/contribute/build-code-and-run-tests/openmetadata-ops) ## Running the OpenMetadata server diff --git a/content/v1.6.x/developers/contribute/build-code-and-run-tests/openmetadata-ops.md b/content/v1.6.x/developers/contribute/build-code-and-run-tests/openmetadata-ops.md new file mode 100644 index 00000000..6366607f --- /dev/null +++ b/content/v1.6.x/developers/contribute/build-code-and-run-tests/openmetadata-ops.md @@ -0,0 +1,54 @@ +--- +title: Understanding openmetadata-ops.sh file +slug: /developers/contribute/build-code-and-run-tests/openmetadata-ops +--- + +# Understanding openmetadata-ops.sh file +Learn how to run the OpenMetadata Ops in development mode by using commands. + +#### Key Commands: +How to run the `openmetadata-ops.sh` file. +```shell +sh bootstrap/openmetadata-ops.sh [OPTIONS] [COMMANDS] +``` + +#### Options: + 1. -c, --config= + 2. -d, --debug + 3. -h, --help Show this help message and exit. + 4. -V, --version Print version information and exit. + +**Example:** +```shell +sh bootstrap/openmetadata-ops.sh --help +``` + +#### Commands: + 1. **migrate** Migrates the OpenMetadata database schema and search index mappings. + + 2. **reindex** Re Indexes data into search engine from command line. + + 3. **repair** Repairs the DATABASE_CHANGE_LOG table which is used to trackall the migrations on the target database. This involves removing entries for the failed migrations and updatethe checksum of migrations already applied on the target database. + + 4. **validate** Checks if the all the migrations haven been applied on the target database. + + 5. **drop-create** Deletes any tables in configured database and creates a new tables based on current version of OpenMetadata. This command also re-creates the search indexes. + + 6. **deploy-pipelines** Deploy all the service pipelines. + + 7. **analyze-tables** Migrate secrets from DB to the configured Secrets Manager. Note that this does not support migrating between external Secrets Managers. + + 8. **changelog** Prints the change log of database migration. + + 9. **check-connection** Checks if a connection can be successfully obtained for the target database + + 10. **info** Shows the list of migrations applied and the pending migration waiting to be applied on the target database + + 11. **migrate-secrets** Migrate secrets from DB to the configured Secrets Manager. Note that this does not support migrating between external Secrets Managers + + 12. **syncEmailFromEnv** Sync the email configuration from environment variables + +**Example:** +```shell +sh bootstrap/openmetadata-ops.sh migration +``` \ No newline at end of file diff --git a/content/v1.6.x/developers/contribute/build-code-and-run-tests/openmetadata-server.md b/content/v1.6.x/developers/contribute/build-code-and-run-tests/openmetadata-server.md index e5749f24..de99982f 100644 --- a/content/v1.6.x/developers/contribute/build-code-and-run-tests/openmetadata-server.md +++ b/content/v1.6.x/developers/contribute/build-code-and-run-tests/openmetadata-server.md @@ -50,6 +50,10 @@ Extract the distribution tar.gz file created on the previous step and run the fo cd open-metadata- sh bootstrap/openmetadata-ops.sh drop-create ``` +{%note%} +Why Needed: The script simplifies the setup and execution of OpenMetadata by handling Java dependencies, configurations, and environment variables automatically. +{%/note%} +**Note** To understand more about openmetadata-ops.sh file click [here](/developers/contribute/build-code-and-run-tests/openmetadata-ops) ## Running the OpenMetadata server diff --git a/content/v1.7.x-SNAPSHOT/developers/contribute/build-code-and-run-tests/openmetadata-ops.md b/content/v1.7.x-SNAPSHOT/developers/contribute/build-code-and-run-tests/openmetadata-ops.md new file mode 100644 index 00000000..6366607f --- /dev/null +++ b/content/v1.7.x-SNAPSHOT/developers/contribute/build-code-and-run-tests/openmetadata-ops.md @@ -0,0 +1,54 @@ +--- +title: Understanding openmetadata-ops.sh file +slug: /developers/contribute/build-code-and-run-tests/openmetadata-ops +--- + +# Understanding openmetadata-ops.sh file +Learn how to run the OpenMetadata Ops in development mode by using commands. + +#### Key Commands: +How to run the `openmetadata-ops.sh` file. +```shell +sh bootstrap/openmetadata-ops.sh [OPTIONS] [COMMANDS] +``` + +#### Options: + 1. -c, --config= + 2. -d, --debug + 3. -h, --help Show this help message and exit. + 4. -V, --version Print version information and exit. + +**Example:** +```shell +sh bootstrap/openmetadata-ops.sh --help +``` + +#### Commands: + 1. **migrate** Migrates the OpenMetadata database schema and search index mappings. + + 2. **reindex** Re Indexes data into search engine from command line. + + 3. **repair** Repairs the DATABASE_CHANGE_LOG table which is used to trackall the migrations on the target database. This involves removing entries for the failed migrations and updatethe checksum of migrations already applied on the target database. + + 4. **validate** Checks if the all the migrations haven been applied on the target database. + + 5. **drop-create** Deletes any tables in configured database and creates a new tables based on current version of OpenMetadata. This command also re-creates the search indexes. + + 6. **deploy-pipelines** Deploy all the service pipelines. + + 7. **analyze-tables** Migrate secrets from DB to the configured Secrets Manager. Note that this does not support migrating between external Secrets Managers. + + 8. **changelog** Prints the change log of database migration. + + 9. **check-connection** Checks if a connection can be successfully obtained for the target database + + 10. **info** Shows the list of migrations applied and the pending migration waiting to be applied on the target database + + 11. **migrate-secrets** Migrate secrets from DB to the configured Secrets Manager. Note that this does not support migrating between external Secrets Managers + + 12. **syncEmailFromEnv** Sync the email configuration from environment variables + +**Example:** +```shell +sh bootstrap/openmetadata-ops.sh migration +``` \ No newline at end of file diff --git a/content/v1.7.x-SNAPSHOT/developers/contribute/build-code-and-run-tests/openmetadata-server.md b/content/v1.7.x-SNAPSHOT/developers/contribute/build-code-and-run-tests/openmetadata-server.md index 1d7cdf31..bb1ae31e 100644 --- a/content/v1.7.x-SNAPSHOT/developers/contribute/build-code-and-run-tests/openmetadata-server.md +++ b/content/v1.7.x-SNAPSHOT/developers/contribute/build-code-and-run-tests/openmetadata-server.md @@ -50,6 +50,10 @@ Extract the distribution tar.gz file created on the previous step and run the fo cd open-metadata- sh bootstrap/openmetadata-ops.sh drop-create ``` +{%note%} +Why Needed: The script simplifies the setup and execution of OpenMetadata by handling Java dependencies, configurations, and environment variables automatically. +{%/note%} +**Note** To understand more about openmetadata-ops.sh file click [here](/developers/contribute/build-code-and-run-tests/openmetadata-ops) ## Running the OpenMetadata server