chore: move shared doc folder

Author: tianzhou

content/docs/api/issue.md

@@ -87,7 +87,7 @@ Inside the plan, create one or more sheets if needed. Then you orchestrate the o
 
 Each spec corresponds to a task. A task is a single change unit. Tasks run in the following order:
 
-<IncludeBlock url="/docs/tutorials/share/task-run-order"></IncludeBlock>
+<IncludeBlock url="/docs/share/tutorials/task-run-order"></IncludeBlock>
 
 If you want to enforce strict running order inside a step/stage. You can specify `dependsOnSpecs` with the previous task.
 

content/docs/change-database/change-workflow.md

@@ -51,7 +51,7 @@ one or more SQL statements to be executed.
 
 Tasks run in the following order:
 
-<IncludeBlock url="/docs/tutorials/share/task-run-order"></IncludeBlock>
+<IncludeBlock url="/docs/share/tutorials/task-run-order"></IncludeBlock>
 
 ### Task Detail
 

content/docs/share/database-permission-table.md

@@ -0,0 +1,8 @@
+| Access Level | Operation                                              | Permission               |
+| ------------ | ------------------------------------------------------ | ------------------------ |
+| Read         | [EXPLAIN](/docs/security/database-permission/explain/) | `databases.queryExplain` |
+|              | [Query](/docs/security/database-permission/query/)     | `databases.query`        |
+|              | [Export](/docs/security/database-permission/export/)   | `databases.export`       |
+| Write        | Data-modifying DML                                     | `databases.queryDML`     |
+|              | DDL                                                    | `databases.queryDDL`     |
+| Admin        | [Admin](/docs/sql-editor/admin-mode/)                  | `instances.adminExecute` |

…utorials/share/create-service-account.md …hare/tutorials/create-service-account.mdcontent/docs/tutorials/share/create-service-account.md renamed to content/docs/share/tutorials/create-service-account.md content/docs/tutorials/share/create-service-account.md renamed to content/docs/share/tutorials/create-service-account.md

@@ -1,5 +1,5 @@
 1.  Log in as the admin user, and go to **Security & Policy > Users & Groups**. Click **+ Add User**, fill in with `api-example`, choose the `DBA` role that is sufficient for this tutorial and click **Confirm**.
-    ![service-account-create](/content/docs/tutorials/share/add-service-account.webp)
+    ![service-account-create](/content/docs/share/tutorials/add-service-account.webp)
 
 1.  Find the newly created service account and click on **Copy Service Key**. We will use this token to authenticate the API calls.
-    ![service-account-key](/content/docs/tutorials/share/service-account-key.webp)
+    ![service-account-key](/content/docs/share/tutorials/service-account-key.webp)

…e/database-workflow-advanced-features.md …s/database-workflow-advanced-features.mdcontent/docs/tutorials/share/database-workflow-advanced-features.md renamed to content/docs/share/tutorials/database-workflow-advanced-features.md content/docs/tutorials/share/database-workflow-advanced-features.md renamed to content/docs/share/tutorials/database-workflow-advanced-features.md

@@ -4,17 +4,17 @@ You may upgrade to Enterprise plan to explore more features.
 
 Go to **Environments** > **Prod**, Find **Rollout policy** section, and choose **Manual rollout** > **Require rolling out by dedicated roles**.
 
-![bb-env-prod-manual-rollout](/content/docs/tutorials/share/bb-env-prod-manual-rollout.webp)
+![bb-env-prod-manual-rollout](/content/docs/share/tutorials/bb-env-prod-manual-rollout.webp)
 
 ### Custom Approval
 
 1. Go to **CI/CD** > **Custom Approval**. Set `Project Owner -> DBA` as Approval flow for **DDL** > **High Risk**.
 
-   ![bb-custom-approval](/content/docs/tutorials/share/bb-custom-approval.webp)
+   ![bb-custom-approval](/content/docs/share/tutorials/bb-custom-approval.webp)
 
 1. Go to **CI/CD** > **Risk Center**. Click **Add rule** and click **Load** for the first template. Click **Add**.
 
-   ![bb-risk-center-ddl-high](/content/docs/tutorials/share/bb-risk-center-ddl-high.webp)
+   ![bb-risk-center-ddl-high](/content/docs/share/tutorials/bb-risk-center-ddl-high.webp)
 
 ### Schema Drift
 
@@ -31,6 +31,6 @@ Bytebase has built-in [schema drift detection](/docs/change-database/drift-detec
 
 1. Go back to Bytebase Console, and click **Databases** > `employee` under `Prod`. Click **Sync Now**. After seeing the success message, refresh the page. You'll see the schema drift. You may configure auto scan on instance detail page to avoid manual sync.
 
-   ![bb-db-schema-drift](/content/docs/tutorials/share/bb-db-schema-drift.webp)
+   ![bb-db-schema-drift](/content/docs/share/tutorials/bb-db-schema-drift.webp)
 
-14. Go to **Database** > **Anomalies**, and you'll see the Schema drift there too.
+1. Go to **Database** > **Anomalies**, and you'll see the Schema drift there too.

…ocs/tutorials/share/database-workflow.md …ocs/share/tutorials/database-workflow.mdcontent/docs/tutorials/share/database-workflow.md renamed to content/docs/share/tutorials/database-workflow.md content/docs/tutorials/share/database-workflow.md renamed to content/docs/share/tutorials/database-workflow.md

@@ -4,7 +4,7 @@ DORA (DevOps Research & Assessment) [pointed out](https://cloud.google.com/archi
 
 But how does it work, really? Here, we present our envisioned Database CI/CD workflow.
 
-![database-devops-workflow](/content/docs/tutorials/share/cicd-workflow.webp)
+![database-devops-workflow](/content/docs/share/tutorials/cicd-workflow.webp)
 
 1. The developer creates a Pull Request containing the SQL script;
 1. SQL Review CI is automatically triggered to review SQL and offers suggestions via a comment in the PR;

…s/tutorials/share/sql-review-not-null.md …s/share/tutorials/sql-review-not-null.mdcontent/docs/tutorials/share/sql-review-not-null.md renamed to content/docs/share/tutorials/sql-review-not-null.md content/docs/tutorials/share/sql-review-not-null.md renamed to content/docs/share/tutorials/sql-review-not-null.md

@@ -1,7 +1,7 @@
 1. Go to **CI/CD > SQL Review** in workspace, choose `Prod` as the environment. Make sure a SQL review policy is attached and enabled on `Prod`.
 
-   ![bb-sql-review](/content/docs/tutorials/share/bb-sql-review.webp)
+   ![bb-sql-review](/content/docs/share/tutorials/bb-sql-review.webp)
 
 1. Click **Edit**, click **PostgreSQL** tab. Make sure `Enforce "NOT NULL" constraints on columns` is enabled. This is to make sure the SQL Review can work.
 
-   ![bb-sql-review-not-null](/content/docs/tutorials/share/bb-sql-review-not-null.webp)
+   ![bb-sql-review-not-null](/content/docs/share/tutorials/bb-sql-review-not-null.webp)