diff --git a/src/content/en/administrator-manual/audit/reports/audit-log-export.mdx b/src/content/en/administrator-manual/audit/reports/audit-log-export.mdx index 66cf6b49..0f139fc7 100644 --- a/src/content/en/administrator-manual/audit/reports/audit-log-export.mdx +++ b/src/content/en/administrator-manual/audit/reports/audit-log-export.mdx @@ -121,7 +121,7 @@ When extracting logs by selecting the current date, since data is accumulated in - Number Type -Supported expressions: `>`, `<`, `<=`, `>=`, `==`, `!=`
Example: `x > `10``, `x == `10`` +Supported expressions: `>`, `<`, `<=`, `>=`, `==`, `!=`
Example: `x > `10``, `x == `10`` - String Type @@ -129,11 +129,11 @@ Supported expressions: `== (equals)`, `!= (not equals)`, `contains`
Example: - Boolean Type -Supported expressions: `== (equals)`, `!= (not equals)`, `&& (and)`, `|| (or)`
Example: `x == `true``,`x && y`, `(x > `0`) && (y == `0`)` +Supported expressions: `== (equals)`, `!= (not equals)`, `&& (and)`, `|| (or)`
Example: `x == `true``,`x && y`, `(x > `0`) && (y == `0`)` - Array Type -Example: `x[? @ == 'value']`, `list[? @ > `10`]` +Example: `x[? @ == 'value']`, `list[? @ > `10`]` (3) You can use the following characters to use multiple conditions together: diff --git a/src/content/en/administrator-manual/databases/connection-management/db-connections.mdx b/src/content/en/administrator-manual/databases/connection-management/db-connections.mdx index d39dfc23..febcc6ef 100644 --- a/src/content/en/administrator-manual/databases/connection-management/db-connections.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/db-connections.mdx @@ -186,7 +186,7 @@ DB Account items are displayed differently depending on the Secret Engine type s * When `Secret Engine` = K/V setting, Username / Password input fields are displayed on the connection information page. * Enter the Vault Path in the Username / Password fields. * Path can be entered in the format `prod_db/data/mysql?username`. - * Based on the example, the actual path in Vault is when the key `username` exists in `prod_db > mysql`. + * Based on the example, the actual path in Vault is when the key `username` exists in `prod_db > mysql`. * The `/data` path in the middle must be added. * When `Secret Engine` = Database setting, Account input field is displayed on the connection information page. * Enter the Vault Path in the Account field. diff --git a/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-yaml-code-syntax-guide.mdx b/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-yaml-code-syntax-guide.mdx index 2f7f0bdd..c00bc13b 100644 --- a/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-yaml-code-syntax-guide.mdx +++ b/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-yaml-code-syntax-guide.mdx @@ -92,7 +92,7 @@ It is a value managed by the system and does not need to be modified. -`spec:`
`<effect>` +`spec:`
`` - diff --git a/src/content/en/administrator-manual/web-apps/wac-quickstart/1027-wac-role-policy-guide.mdx b/src/content/en/administrator-manual/web-apps/wac-quickstart/1027-wac-role-policy-guide.mdx index da6f33f9..95cf3622 100644 --- a/src/content/en/administrator-manual/web-apps/wac-quickstart/1027-wac-role-policy-guide.mdx +++ b/src/content/en/administrator-manual/web-apps/wac-quickstart/1027-wac-role-policy-guide.mdx @@ -92,7 +92,7 @@ System-managed value, no modification needed -`spec:`
`<effect>` +`spec:`
`` - diff --git a/src/content/en/administrator-manual/web-apps/wac-quickstart/1028-wac-rbac-guide.mdx b/src/content/en/administrator-manual/web-apps/wac-quickstart/1028-wac-rbac-guide.mdx index 17d9f12f..de12a748 100644 --- a/src/content/en/administrator-manual/web-apps/wac-quickstart/1028-wac-rbac-guide.mdx +++ b/src/content/en/administrator-manual/web-apps/wac-quickstart/1028-wac-rbac-guide.mdx @@ -122,7 +122,7 @@ System-managed value, no modification needed -`spec:`
`<effect>` +`spec:`
`` - diff --git a/src/content/en/installation/installation/comparison-of-setupsh-and-setupv2sh.mdx b/src/content/en/installation/installation/comparison-of-setupsh-and-setupv2sh.mdx index 9f070f3a..0b2117cc 100644 --- a/src/content/en/installation/installation/comparison-of-setupsh-and-setupv2sh.mdx +++ b/src/content/en/installation/installation/comparison-of-setupsh-and-setupv2sh.mdx @@ -25,12 +25,12 @@ This document examines how these two installation programs work, their features, * Installs Container Engine and Compose Tool if not found. * Container Engine: Docker or Podman * Compose Tool: Docker Compose -* Installs package.tar.gz for Compose at the `./querypie/<version>` path. +* Installs package.tar.gz for Compose at the `./querypie/` path. * Checks SELinux settings and performs `chcon` command for Container Volume Mount. * Automatically fills in setting values in the environment variable configuration file `.env`. * Downloads Container Images. * Performs QueryPie MySQL Migration and runs QueryPie App Container. -* Creates a Symbolic Link `./querypie/current` pointing to `./querypie/<version>` to indicate the currently running version. +* Creates a Symbolic Link `./querypie/current` pointing to `./querypie/` to indicate the currently running version. #### Additional Features of setup.v2.sh for Upgrade, Deletion, etc. @@ -49,7 +49,7 @@ setup.v2.sh provides other major features in addition to product installation. | Image Registry | `harbor.chequer.io/querypie/` | `docker.io/querypie/` | | Environment Variable Configuration File | `compose-env` | `.env` | | Compose as Plugin | Not supported
Uses `docker-compose` command | Supported
Uses `docker compose` or `podman compose` command | -| MySQL Data Dir | `./querypie/<version>/mysql/` | `./querypie/mysql/` | +| MySQL Data Dir | `./querypie//mysql/` | `./querypie/mysql/` | | Application Log | `/var/log/querypie/` - 10.2.x
`./querypie/log/` - 11.x | `./querypie/log/` | | Symlink for Running Version | (None) | `./querypie/current` | diff --git a/src/content/en/installation/installation/installation-guide-setupv2sh.mdx b/src/content/en/installation/installation/installation-guide-setupv2sh.mdx index 19c3dc19..e1628bc0 100644 --- a/src/content/en/installation/installation/installation-guide-setupv2sh.mdx +++ b/src/content/en/installation/installation/installation-guide-setupv2sh.mdx @@ -221,7 +221,7 @@ Values set in .env such as DB_PASSWORD, REDIS_PASSWORD, KEY_ENCRYPTION_KEY must Please be careful not to expose these values to others. -Replace the `<customer-proxy-address>` part below with your customer's Proxy access IP or domain and execute the query. +Replace the `` part below with your customer's Proxy access IP or domain and execute the query. This address should not have a Scheme such as `http` or `https` attached. @@ -246,7 +246,7 @@ When you attempt to log in from User Agent, after authentication through a web b Connect to QueryPie Database and register the address for KAC Proxy access. -Replace the `<customer-proxy-fqdn>` part below with your customer's Proxy access IP or domain and execute the query. +Replace the `` part below with your customer's Proxy access IP or domain and execute the query. As a special note, unlike DAC/SAC settings, you can freely enter Schemes such as `http` or `https`. diff --git a/src/content/en/installation/installation/installation-guide-simple-configuration.mdx b/src/content/en/installation/installation/installation-guide-simple-configuration.mdx index 403e9782..97ffb682 100644 --- a/src/content/en/installation/installation/installation-guide-simple-configuration.mdx +++ b/src/content/en/installation/installation/installation-guide-simple-configuration.mdx @@ -118,7 +118,7 @@ Login Succeeded ### compose-env Configuration -When you run the `./setup.sh` script, it creates configuration files such as `docker-compose.yml` and `compose-env` in the `querypie/<version>/` directory. +When you run the `./setup.sh` script, it creates configuration files such as `docker-compose.yml` and `compose-env` in the `querypie//` directory. Move into this directory and edit the configuration file named `compose-env`. For descriptions of each environment variable, please refer to the following document: [Container Environment Variables](../container-environment-variables) @@ -336,7 +336,7 @@ Values set in compose-env such as DB_PASSWORD, REDIS_PASSWORD, KEY_ENCRYPTION_KE Please be careful not to expose these values to others. -Replace the `<customer-proxy-address>` part below with your customer's Proxy access IP or domain and execute the query. +Replace the `` part below with your customer's Proxy access IP or domain and execute the query. This address should not have a Scheme such as `http` or `https` attached. @@ -361,7 +361,7 @@ When you attempt to log in from User Agent, after authentication through a web b Connect to QueryPie Database and register the address for KAC Proxy access. -Replace the `<customer-proxy-fqdn>` part below with your customer's Proxy access IP or domain and execute the query. +Replace the `` part below with your customer's Proxy access IP or domain and execute the query. As a special note, unlike DAC/SAC settings, you can freely enter Schemes such as `http` or `https`. diff --git a/src/content/en/installation/prerequisites/configuring-rootless-mode-with-podman.mdx b/src/content/en/installation/prerequisites/configuring-rootless-mode-with-podman.mdx index b72a91f7..078cea6e 100644 --- a/src/content/en/installation/prerequisites/configuring-rootless-mode-with-podman.mdx +++ b/src/content/en/installation/prerequisites/configuring-rootless-mode-with-podman.mdx @@ -106,7 +106,7 @@ Created symlink /home/ec2-user/.config/systemd/user/default.target.wants/podman- When Using Separately Configured MySQL -If you use a separately configured MySQL instead of running MySQL on one Linux server using the default `./querypie/<version>/compose.yml`, you can change the systemd service operation scope. +If you use a separately configured MySQL instead of running MySQL on one Linux server using the default `./querypie//compose.yml`, you can change the systemd service operation scope. You just need to not activate `podman-querypie-database.service`. You can turn off running systemd services with the following command. diff --git a/src/content/en/user-manual/database-access-control/setting-default-privilege.mdx b/src/content/en/user-manual/database-access-control/setting-default-privilege.mdx index c9a19271..c1b093d2 100644 --- a/src/content/en/user-manual/database-access-control/setting-default-privilege.mdx +++ b/src/content/en/user-manual/database-access-control/setting-default-privilege.mdx @@ -30,7 +30,7 @@ QueryPie Web > Database Access Control > Databases > Privileges > De -1. Click the `Edit` button or `> Go to Settings` link on the right of Privileges. +1. Click the `Edit` button or `> Go to Settings` link on the right of Privileges. 2. In the Privilege section, select the Privilege to use as the default value among the granted permissions. 3. Click the Save button to complete the Default Privilege setting. diff --git a/src/content/en/user-manual/multi-agent.mdx b/src/content/en/user-manual/multi-agent.mdx index 3cc87f1b..290f0a7e 100644 --- a/src/content/en/user-manual/multi-agent.mdx +++ b/src/content/en/user-manual/multi-agent.mdx @@ -246,7 +246,7 @@ When you don't have the necessary account permissions to connect to a server, yo **Notes** -* If the QueryPie administrator disables `Server Privilege Request` in the `Admin > General > Workflow Configurations` setting, the `Request Server Privilege` button in the agent is also disabled. +* If the QueryPie administrator disables `Server Privilege Request` in the `Admin > General > Workflow Configurations` setting, the `Request Server Privilege` button in the agent is also disabled. diff --git a/src/content/ja/administrator-manual/audit/reports/audit-log-export.mdx b/src/content/ja/administrator-manual/audit/reports/audit-log-export.mdx index 35931967..b8438cfd 100644 --- a/src/content/ja/administrator-manual/audit/reports/audit-log-export.mdx +++ b/src/content/ja/administrator-manual/audit/reports/audit-log-export.mdx @@ -121,7 +121,7 @@ Administrator > Audit > General > Audit Log Export > Create New Task - Number Type -サポートする表現式: `>`, `<`, `<=`, `>=`, `==`, `!=`
例: `x > `10``, `x == `10`` +サポートする表現式: `>`, `<`, `<=`, `>=`, `==`, `!=`
例: `x > `10``, `x == `10`` - String Type @@ -129,11 +129,11 @@ Administrator > Audit > General > Audit Log Export > Create New Task - Boolean Type -サポートする表現式: `== (equals)`, `!= (not equals)`, `&& (and)`, `|| (or)`
例: `x == `true``,`x && y`, `(x > `0`) && (y == `0`)` +サポートする表現式: `== (equals)`, `!= (not equals)`, `&& (and)`, `|| (or)`
例: `x == `true``,`x && y`, `(x > `0`) && (y == `0`)` - Array Type -例: `x[? @ == 'value']`, `list[? @ > `10`]` +例: `x[? @ == 'value']`, `list[? @ > `10`]` (3) 複数の条件を一緒に使用するために以下の文字を活用できます。 diff --git a/src/content/ja/administrator-manual/databases/connection-management/db-connections.mdx b/src/content/ja/administrator-manual/databases/connection-management/db-connections.mdx index 12b065ce..555affc0 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/db-connections.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/db-connections.mdx @@ -186,7 +186,7 @@ Secret Store設定に保存されたSecret Engineタイプに 따라DB Account * `Secret Engine` = K/V設定時、コネクション情報ページでUsername / Password入力項目が表示されます。 * Username / Password項目にVaultのPathを入力します。 * Pathの形態は`prod_db/data/mysql?username`形態で入力できます。 - * 例基準実際にVault内の経路は`prod_db > mysql`のkeyが`username`の場合です。 + * 例基準実際にVault内の経路は`prod_db > mysql`のkeyが`username`の場合です。 * 中間の`/data`経路を追加しなければなりません。 * `Secret Engine` = Database設定時、コネクション情報ページでAccount入力項目が表示されます。 * Account項目にVaultのPathを入力します。 diff --git a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-yaml-code-syntax-guide.mdx b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-yaml-code-syntax-guide.mdx index 2b92ad4c..8c0a9770 100644 --- a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-yaml-code-syntax-guide.mdx +++ b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-yaml-code-syntax-guide.mdx @@ -92,7 +92,7 @@ O -`spec:`
`<effect>` +`spec:`
`` - diff --git a/src/content/ja/administrator-manual/web-apps/wac-quickstart/1027-wac-role-policy-guide.mdx b/src/content/ja/administrator-manual/web-apps/wac-quickstart/1027-wac-role-policy-guide.mdx index d6a784c9..119c0d68 100644 --- a/src/content/ja/administrator-manual/web-apps/wac-quickstart/1027-wac-role-policy-guide.mdx +++ b/src/content/ja/administrator-manual/web-apps/wac-quickstart/1027-wac-role-policy-guide.mdx @@ -92,7 +92,7 @@ WACのポリシーはYAML形式で記述され、その基本構造は以下の -`spec:`
`<effect>` +`spec:`
`` - diff --git a/src/content/ja/administrator-manual/web-apps/wac-quickstart/1028-wac-rbac-guide.mdx b/src/content/ja/administrator-manual/web-apps/wac-quickstart/1028-wac-rbac-guide.mdx index 48867a34..44aadda9 100644 --- a/src/content/ja/administrator-manual/web-apps/wac-quickstart/1028-wac-rbac-guide.mdx +++ b/src/content/ja/administrator-manual/web-apps/wac-quickstart/1028-wac-rbac-guide.mdx @@ -122,7 +122,7 @@ spec: -`spec:`
`<effect>` +`spec:`
`` - diff --git a/src/content/ja/installation/installation/comparison-of-setupsh-and-setupv2sh.mdx b/src/content/ja/installation/installation/comparison-of-setupsh-and-setupv2sh.mdx index c3c059d9..d8b28fa8 100644 --- a/src/content/ja/installation/installation/comparison-of-setupsh-and-setupv2sh.mdx +++ b/src/content/ja/installation/installation/comparison-of-setupsh-and-setupv2sh.mdx @@ -25,12 +25,12 @@ setup.v2.shはQueryPie Community Editionリリースとともに提供されるQ * Container Engine、Compose Toolが発見されない場合、これらをインストールします。 * Container Engine：DockerまたはPodman * Compose Tool: Docker Compose -* `./querypie/<version>`経路にComposeのためのpackage.tar.gzをインストールします。 +* `./querypie/`経路にComposeのためのpackage.tar.gzをインストールします。 * SELinux設定を点検し、Container Volume Mountのための`chcon`コマンドを実行します。 * 環境変数設定ファイル`.env`の設定値を自動的に埋めます。 * Container Imageをダウンロードします。 * QueryPie MySQLのMigrationを実行し、QueryPie App Containerを実行します。 -* `./querypie/current`というSymbolic Linkを`./querypie/<version>`に接続して、現在動作中のバージョンを明示します。 +* `./querypie/current`というSymbolic Linkを`./querypie/`に接続して、現在動作中のバージョンを明示します。 #### setup.v2.shのアップグレード、削除など追加機能 @@ -49,7 +49,7 @@ setup.v2.shは製品のインストール以外にも他の主要機能を提供 | Image Registry | `harbor.chequer.io/querypie/` | `docker.io/querypie/` | | 環境変数設定ファイル | `compose-env` | `.env` | | Compose as Plugin | 未サポート
`docker-compose`コマンドを使用 | サポート
`docker compose`または`podman compose`コマンドを使用 | -| MySQL Data Dir | `./querypie/<version>/mysql/` | `./querypie/mysql/` | +| MySQL Data Dir | `./querypie//mysql/` | `./querypie/mysql/` | | Application Log | `/var/log/querypie/` - 10.2.x
`./querypie/log/` - 11.x | `./querypie/log/` | | 動作中バージョンのSymlink | （なし） | `./querypie/current` | diff --git a/src/content/ja/installation/installation/installation-guide-setupv2sh.mdx b/src/content/ja/installation/installation/installation-guide-setupv2sh.mdx index cfe9dc3d..234910c8 100644 --- a/src/content/ja/installation/installation/installation-guide-setupv2sh.mdx +++ b/src/content/ja/installation/installation/installation-guide-setupv2sh.mdx @@ -221,7 +221,7 @@ Database接続設定過程でQueryPie MySQLのHostname、Username、Passwordが 他の人にこの値を露出しないよう注意してください。 -以下`<customer-proxy-address>`部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。 +以下``部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。 該当アドレスは`http` `https`のようなSchemeを付けてはいけません。 @@ -246,7 +246,7 @@ User Agentからログインを試みると、ウェブブラウザを通じて QueryPie Databaseに接続して、KACのProxy接続のためのアドレスを登録します。 -以下`<customer-proxy-fqdn>`部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。 +以下``部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。 特記事項としてDAC/SAC設定とは異なり`http` `https`のようなSchemeを自由に入力可能です。 diff --git a/src/content/ja/installation/installation/installation-guide-simple-configuration.mdx b/src/content/ja/installation/installation/installation-guide-simple-configuration.mdx index 5b284d54..dff3d9ff 100644 --- a/src/content/ja/installation/installation/installation-guide-simple-configuration.mdx +++ b/src/content/ja/installation/installation/installation-guide-simple-configuration.mdx @@ -118,7 +118,7 @@ Login Succeeded ### compose-env設定 -`./setup.sh`スクリプトを実行すると、`querypie/<version>/`ディレクトリ内に`docker-compose.yml`、`compose-env`など設定ファイルを生成します。 +`./setup.sh`スクリプトを実行すると、`querypie//`ディレクトリ内に`docker-compose.yml`、`compose-env`など設定ファイルを生成します。 このディレクトリ内に移動して、`compose-env`という名前の設定ファイルを編集します。 各環境変数に関する説明は次の文書を参照してください：[コンテナ環境変数案内](../container-environment-variables) @@ -336,7 +336,7 @@ compose-envに設定された値のうちDB_PASSWORD、REDIS_PASSWORD、KEY_ENCR 他の人にこの値を露出しないよう注意してください。 -以下`<customer-proxy-address>`部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。 +以下``部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。 該当アドレスは`http` `https`のようなSchemeを付けてはいけません。 @@ -361,7 +361,7 @@ User Agentからログインを試みると、ウェブブラウザを通じて QueryPie Databaseに接続して、KACのProxy接続のためのアドレスを登録します。 -以下`<customer-proxy-fqdn>`部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。 +以下``部分を顧客社のProxy接続IPまたはドメインに置き換えてクエリを実行します。 特記事項としてDAC/SAC設定とは異なり`http` `https`のようなSchemeを自由に入力可能です。 diff --git a/src/content/ja/installation/prerequisites/configuring-rootless-mode-with-podman.mdx b/src/content/ja/installation/prerequisites/configuring-rootless-mode-with-podman.mdx index 378166c0..cad9cfdd 100644 --- a/src/content/ja/installation/prerequisites/configuring-rootless-mode-with-podman.mdx +++ b/src/content/ja/installation/prerequisites/configuring-rootless-mode-with-podman.mdx @@ -106,7 +106,7 @@ Created symlink /home/ec2-user/.config/systemd/user/default.target.wants/podman- 別途構成されたMySQLを使用する場合 -基本提供される`./querypie/<version>/compose.yml`を利用して、1つのLinuxサーバでMySQLを実行せず、別途構成されたMySQLを使用する場合、systemd service動作範囲を変更すればよいです。 +基本提供される`./querypie//compose.yml`を利用して、1つのLinuxサーバでMySQLを実行せず、別途構成されたMySQLを使用する場合、systemd service動作範囲を変更すればよいです。 `podman-querypie-database.service`を動作させなければよいです。 動作中のsystemd serviceを次のコマンドでオフにできます。 diff --git a/src/content/ja/user-manual/database-access-control/setting-default-privilege.mdx b/src/content/ja/user-manual/database-access-control/setting-default-privilege.mdx index 3791f328..6e6ab50d 100644 --- a/src/content/ja/user-manual/database-access-control/setting-default-privilege.mdx +++ b/src/content/ja/user-manual/database-access-control/setting-default-privilege.mdx @@ -30,7 +30,7 @@ QueryPie Web > Database Access Control > Databases > Privileges > De -1. Privileges右側の`Edit`ボタンまたは`> Go to Settings`リンクをクリックします。 +1. Privileges右側の`Edit`ボタンまたは`> Go to Settings`リンクをクリックします。 2. Privilege項目で付与された権限の中から基本値で使用するPrivilegeを選択します。 3. SaveボタンをクリックしてDefault Privilege設定を完了します。 diff --git a/src/content/ja/user-manual/multi-agent.mdx b/src/content/ja/user-manual/multi-agent.mdx index 89df76df..14fa6404 100644 --- a/src/content/ja/user-manual/multi-agent.mdx +++ b/src/content/ja/user-manual/multi-agent.mdx @@ -246,7 +246,7 @@ Multi-Agent > Setting > Kubernetes **注意事項** -* QueryPie管理者が`Admin > General > Workflow Configurations`設定で`Server Privilege Request`を非活性化した場合、エージェントの`Request Server Privilege`ボタンも非活性化されます。 +* QueryPie管理者が`Admin > General > Workflow Configurations`設定で`Server Privilege Request`を非活性化した場合、エージェントの`Request Server Privilege`ボタンも非活性化されます。 diff --git a/src/content/ko/administrator-manual/audit/reports/audit-log-export.mdx b/src/content/ko/administrator-manual/audit/reports/audit-log-export.mdx index d2e38baf..f0e874c4 100644 --- a/src/content/ko/administrator-manual/audit/reports/audit-log-export.mdx +++ b/src/content/ko/administrator-manual/audit/reports/audit-log-export.mdx @@ -121,7 +121,7 @@ Administrator > Audit > General > Audit Log Export > Create New Task - Number Type -지원하는 표현식 : `>`, `<`, `<=`, `>=`, `==`, `!=`
예 : `x > `10``, `x == `10`` +지원하는 표현식 : `>`, `<`, `<=`, `>=`, `==`, `!=`
예 : `x > `10``, `x == `10`` - String Type @@ -129,11 +129,11 @@ Administrator > Audit > General > Audit Log Export > Create New Task - Boolean Type -지원하는 표현식 : `== (equals)`, `!= (not equals)`, `&& (and)`, `|| (or)`
예 : `x == `true``,`x && y`, `(x > `0`) && (y == `0`)` +지원하는 표현식 : `== (equals)`, `!= (not equals)`, `&& (and)`, `|| (or)`
예 : `x == `true``,`x && y`, `(x > `0`) && (y == `0`)` - Array Type -예 : `x[? @ == 'value']`, `list[? @ > `10`]` +예 : `x[? @ == 'value']`, `list[? @ > `10`]` (3) 여러 조건을 함께 사용하기 위해 아래의 문자를 활용할 수 있습니다. diff --git a/src/content/ko/administrator-manual/databases/connection-management/db-connections.mdx b/src/content/ko/administrator-manual/databases/connection-management/db-connections.mdx index a430ee27..44451edc 100644 --- a/src/content/ko/administrator-manual/databases/connection-management/db-connections.mdx +++ b/src/content/ko/administrator-manual/databases/connection-management/db-connections.mdx @@ -186,7 +186,7 @@ Secret Store 설정에 저장된 Secret Engine 타입에 따라 DB Account 항 * `Secret Engine` = K/V 설정시, 커넥션 정보 페이지에서 Username / Password 입력 항목이 표시됩니다. * Username / Password 항목에 Vault 의 Path 를 입력합니다. * Path 의 형태는 `prod_db/data/mysql?username` 형태로 입력할 수 있습니다. - * 예시 기준 실제로 Vault 내의 경로는 `prod_db > mysql` 의 key 가 `username` 인 경우입니다. + * 예시 기준 실제로 Vault 내의 경로는 `prod_db > mysql` 의 key 가 `username` 인 경우입니다. * 중간의 `/data` 경로를 추가해야합니다. * `Secret Engine` = Database 설정시, 커넥션 정보 페이지에서 Account 입력 항목이 표시됩니다. * Account 항목에 Vault 의 Path 를 입력합니다. diff --git a/src/content/ko/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-yaml-code-syntax-guide.mdx b/src/content/ko/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-yaml-code-syntax-guide.mdx index cc422766..90c1945b 100644 --- a/src/content/ko/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-yaml-code-syntax-guide.mdx +++ b/src/content/ko/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-yaml-code-syntax-guide.mdx @@ -92,7 +92,7 @@ O -`spec:`
`<effect>` +`spec:`
`` - diff --git a/src/content/ko/administrator-manual/web-apps/wac-quickstart/1027-wac-role-policy-guide.mdx b/src/content/ko/administrator-manual/web-apps/wac-quickstart/1027-wac-role-policy-guide.mdx index b4251924..0ec425e4 100644 --- a/src/content/ko/administrator-manual/web-apps/wac-quickstart/1027-wac-role-policy-guide.mdx +++ b/src/content/ko/administrator-manual/web-apps/wac-quickstart/1027-wac-role-policy-guide.mdx @@ -92,7 +92,7 @@ WAC의 정책은 YAML 형식으로 작성되며, 그 기본 구조는 다음과 -`spec:`
`<effect>` +`spec:`
`` - diff --git a/src/content/ko/administrator-manual/web-apps/wac-quickstart/1028-wac-rbac-guide.mdx b/src/content/ko/administrator-manual/web-apps/wac-quickstart/1028-wac-rbac-guide.mdx index 40c4b149..9511d815 100644 --- a/src/content/ko/administrator-manual/web-apps/wac-quickstart/1028-wac-rbac-guide.mdx +++ b/src/content/ko/administrator-manual/web-apps/wac-quickstart/1028-wac-rbac-guide.mdx @@ -122,7 +122,7 @@ spec: -`spec:`
`<effect>` +`spec:`
`` - diff --git a/src/content/ko/installation/installation/comparison-of-setupsh-and-setupv2sh.mdx b/src/content/ko/installation/installation/comparison-of-setupsh-and-setupv2sh.mdx index ff12964b..5db39a81 100644 --- a/src/content/ko/installation/installation/comparison-of-setupsh-and-setupv2sh.mdx +++ b/src/content/ko/installation/installation/comparison-of-setupsh-and-setupv2sh.mdx @@ -25,12 +25,12 @@ setup.v2.sh 는 QueryPie Community Edition 출시와 함께 제공되는 QueryPi * Container Engine, Compose Tool 이 발견되지 않은 경우, 이를 설치합니다. * Container Engine : Docker 또는 Podman * Compose Tool: Docker Compose -* `./querypie/<version>` 경로에 Compose 를 위한 package.tar.gz 을 설치합니다. +* `./querypie/` 경로에 Compose 를 위한 package.tar.gz 을 설치합니다. * SELinux 설정을 점검하고, Container Volume Mount 를 위한 `chcon` 명령을 수행합니다. * 환경변수 설정파일 `.env` 의 설정값을 자동으로 채웁니다. * Container Image 를 내려받습니다. * QueryPie MySQL 의 Migration 을 수행하고, QueryPie App Container 를 실행합니다. -* `./querypie/current` 라는 Symbolic Link 를 `./querypie/<version>` 으로 연결하여, 현재 작동 중인 버전을 명시합니다. +* `./querypie/current` 라는 Symbolic Link 를 `./querypie/` 으로 연결하여, 현재 작동 중인 버전을 명시합니다. #### setup.v2.sh 의 업그레이드, 삭제 등 추가 기능 @@ -49,7 +49,7 @@ setup.v2.sh 는 제품의 설치 외에도 다른 주요 기능을 제공합니 | Image Registry | `harbor.chequer.io/querypie/` | `docker.io/querypie/` | | 환경변수 설정파일 | `compose-env` | `.env` | | Compose as Plugin | 미지원
`docker-compose` 명령을 사용 | 지원
`docker compose` 또는 `podman compose` 명령을 사용 | -| MySQL Data Dir | `./querypie/<version>/mysql/` | `./querypie/mysql/` | +| MySQL Data Dir | `./querypie//mysql/` | `./querypie/mysql/` | | Application Log | `/var/log/querypie/` - 10.2.x
`./querypie/log/` - 11.x | `./querypie/log/` | | 작동 중 버전의 Symlink | (없음) | `./querypie/current` | diff --git a/src/content/ko/installation/installation/installation-guide-setupv2sh.mdx b/src/content/ko/installation/installation/installation-guide-setupv2sh.mdx index 8123cb0d..fbbd825e 100644 --- a/src/content/ko/installation/installation/installation-guide-setupv2sh.mdx +++ b/src/content/ko/installation/installation/installation-guide-setupv2sh.mdx @@ -221,7 +221,7 @@ Database 연결 설정 과정에서 QueryPie MySQL 의 Hostname, Username, Passw 다른 사람에게 이 값을 노출하지 않도록 주의하여 주세요. -아래 `<customer-proxy-address>` 부분을 고객사의 Proxy 접속 IP 혹은 도메인으로 갈음하여 쿼리를 수행합니다. +아래 `` 부분을 고객사의 Proxy 접속 IP 혹은 도메인으로 갈음하여 쿼리를 수행합니다. 해당 주소는 `http` `https` 와 같은 Scheme 을 붙여서는 안됩니다. @@ -246,7 +246,7 @@ User Agent 에서 로그인을 시도하면, 웹브라우저를 통해 인증을 QueryPie Database 에 접속하여, KAC 의 Proxy 접속을 위한 주소를 등록합니다. -아래 `<customer-proxy-fqdn>` 부분을 고객사의 Proxy 접속 IP 혹은 도메인으로 갈음하여 쿼리를 수행합니다. +아래 `` 부분을 고객사의 Proxy 접속 IP 혹은 도메인으로 갈음하여 쿼리를 수행합니다. 특이사항으로 DAC/SAC 설정과는 다르게 `http` `https` 와 같은 Scheme을 자유롭게 입력 가능합니다. diff --git a/src/content/ko/installation/installation/installation-guide-simple-configuration.mdx b/src/content/ko/installation/installation/installation-guide-simple-configuration.mdx index 83727658..91bd0942 100644 --- a/src/content/ko/installation/installation/installation-guide-simple-configuration.mdx +++ b/src/content/ko/installation/installation/installation-guide-simple-configuration.mdx @@ -118,7 +118,7 @@ Login Succeeded ### compose-env 설정 -`./setup.sh` 스크립트를 실행하면, `querypie/<version>/` 디렉토리 안에 `docker-compose.yml`, `compose-env` 등 설정 파일을 생성하게 됩니다. +`./setup.sh` 스크립트를 실행하면, `querypie//` 디렉토리 안에 `docker-compose.yml`, `compose-env` 등 설정 파일을 생성하게 됩니다. 이 디렉토리 안으로 이동하여, `compose-env` 라는 이름의 설정 파일을 편집합니다. 각 환경변수에 대한 설명은 다음 문서를 참조하여 주세요: [컨테이너 환경변수 안내](../container-environment-variables) @@ -336,7 +336,7 @@ compose-env 에 설정된 값 중 DB_PASSWORD, REDIS_PASSWORD, KEY_ENCRYPTION_KE 다른 사람에게 이 값을 노출하지 않도록 주의하여 주세요. -아래 `<customer-proxy-address>` 부분을 고객사의 Proxy 접속 IP 혹은 도메인으로 갈음하여 쿼리를 수행합니다. +아래 `` 부분을 고객사의 Proxy 접속 IP 혹은 도메인으로 갈음하여 쿼리를 수행합니다. 해당 주소는 `http` `https` 와 같은 Scheme 을 붙여서는 안됩니다. @@ -361,7 +361,7 @@ User Agent 에서 로그인을 시도하면, 웹브라우저를 통해 인증을 QueryPie Database 에 접속하여, KAC 의 Proxy 접속을 위한 주소를 등록합니다. -아래 `<customer-proxy-fqdn>` 부분을 고객사의 Proxy 접속 IP 혹은 도메인으로 갈음하여 쿼리를 수행합니다. +아래 `` 부분을 고객사의 Proxy 접속 IP 혹은 도메인으로 갈음하여 쿼리를 수행합니다. 특이사항으로 DAC/SAC 설정과는 다르게 `http` `https` 와 같은 Scheme을 자유롭게 입력 가능합니다. diff --git a/src/content/ko/installation/prerequisites/configuring-rootless-mode-with-podman.mdx b/src/content/ko/installation/prerequisites/configuring-rootless-mode-with-podman.mdx index 500bd4f2..60450965 100644 --- a/src/content/ko/installation/prerequisites/configuring-rootless-mode-with-podman.mdx +++ b/src/content/ko/installation/prerequisites/configuring-rootless-mode-with-podman.mdx @@ -106,7 +106,7 @@ Created symlink /home/ec2-user/.config/systemd/user/default.target.wants/podman- 별도 구성된 MySQL 을 사용하는 경우 -기본 제공되는 `./querypie/<version>/compose.yml` 을 이용해, 하나의 리눅스 서버에서 MySQL 를 실행하지 않고, 별도로 구성된 MySQL 을 사용하는 경우, systemd service 작동 범위를 변경하면 됩니다. +기본 제공되는 `./querypie//compose.yml` 을 이용해, 하나의 리눅스 서버에서 MySQL 를 실행하지 않고, 별도로 구성된 MySQL 을 사용하는 경우, systemd service 작동 범위를 변경하면 됩니다. `podman-querypie-database.service` 를 작동시키지 않으면 됩니다. 작동 중인 systemd service 를 다음의 명령으로 끌 수 있습니다. diff --git a/src/content/ko/user-manual/database-access-control/setting-default-privilege.mdx b/src/content/ko/user-manual/database-access-control/setting-default-privilege.mdx index 7537eac7..0d07f4cd 100644 --- a/src/content/ko/user-manual/database-access-control/setting-default-privilege.mdx +++ b/src/content/ko/user-manual/database-access-control/setting-default-privilege.mdx @@ -30,7 +30,7 @@ QueryPie Web > Database Access Control > Databases > Privileges > De -1. Privileges 우측에 `Edit` 버튼 또는 `> Go to Settings` 링크를 클릭합니다. +1. Privileges 우측에 `Edit` 버튼 또는 `> Go to Settings` 링크를 클릭합니다. 2. Privilege 항목에서 부여받은 권한 중 기본 값으로 사용할 Privilege 를 선택합니다. 3. Save 버튼을 클릭하여 Default Privilege 설정을 완료합니다. diff --git a/src/content/ko/user-manual/multi-agent.mdx b/src/content/ko/user-manual/multi-agent.mdx index 08b310a7..0c060f6c 100644 --- a/src/content/ko/user-manual/multi-agent.mdx +++ b/src/content/ko/user-manual/multi-agent.mdx @@ -246,7 +246,7 @@ Multi-Agent > Setting > Kubernetes **유의 사항** -* QueryPie 관리자가 `Admin > General > Workflow Configurations` 설정에서 `Server Privilege Request`를 비활성화한 경우, 에이전트의 `Request Server Privilege` 버튼도 비활성화됩니다. +* QueryPie 관리자가 `Admin > General > Workflow Configurations` 설정에서 `Server Privilege Request`를 비활성화한 경우, 에이전트의 `Request Server Privilege` 버튼도 비활성화됩니다.