From 6280152da1adc85a481308fa4a69cb943aa525a5 Mon Sep 17 00:00:00 2001 From: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Date: Mon, 6 Nov 2023 12:23:59 -0500 Subject: [PATCH] Fix links and liquid formatting error (#5512) Signed-off-by: Fanit Kolchina --- .../configuring-data-prepper.md | 12 ++++++------ _data-prepper/pipelines/pipelines.md | 6 +++--- _query-dsl/full-text/match.md | 2 +- 3 files changed, 10 insertions(+), 10 deletions(-) diff --git a/_data-prepper/managing-data-prepper/configuring-data-prepper.md b/_data-prepper/managing-data-prepper/configuring-data-prepper.md index 0c91b37e2c9..bcff65ed4c1 100644 --- a/_data-prepper/managing-data-prepper/configuring-data-prepper.md +++ b/_data-prepper/managing-data-prepper/configuring-data-prepper.md @@ -151,11 +151,11 @@ sts_role_arn | No | String | The AWS Security Token Service (AWS STS) role to refresh_interval | No | Duration | The refreshment interval for AWS secrets extension plugin to poll new secret values. Defaults to `PT1H`. See [Automatically refreshing secrets](#automatically-refreshing-secrets) for details. #### Reference secrets - +ß In `pipelines.yaml`, secret values can be referenced within the pipeline plugins using the following formats: -* plaintext: `${{aws_secrets:}}`. -* JSON (key-value pairs): `${{aws_secrets::}}` +* plaintext: `{% raw %}${{aws_secrets:}}{% endraw %}`. +* JSON (key-value pairs): `{% raw %}${{aws_secrets::}}{% endraw %}` Replace `` with the corresponding secret config ID under `/extensions/aws/secrets`. Replace `` with the desired key in the secret JSON value. The secret value reference string format can be interpreted for the following plugin setting data types: @@ -194,9 +194,9 @@ After `` is configured, you can reference the IDs in your ``` sink: - opensearch: - hosts: [ "${{aws_secrets:host-secret-config}}" ] - username: "${{aws_secrets:credential-secret-config:username}}" - password: "${{aws_secrets:credential-secret-config:password}}" + hosts: [ {% raw %}"${{aws_secrets:host-secret-config}}"{% endraw %} ] + username: {% raw %}"${{aws_secrets:credential-secret-config:username}}"{% endraw %} + password: {% raw %}"${{aws_secrets:credential-secret-config:password}}"{% endraw %} index: "test-migration" ``` diff --git a/_data-prepper/pipelines/pipelines.md b/_data-prepper/pipelines/pipelines.md index 87c8ce57558..e897ed55964 100644 --- a/_data-prepper/pipelines/pipelines.md +++ b/_data-prepper/pipelines/pipelines.md @@ -343,9 +343,9 @@ simple-sample-pipeline: ... sink: - opensearch: - hosts: [ "${{aws_secrets:host-secret-config}}" ] - username: "${{aws_secrets:credential-secret-config:username}}" - password: "${{aws_secrets:credential-secret-config:password}}" + hosts: [ {% raw %}"${{aws_secrets:host-secret-config}}"{% endraw %} ] + username: {% raw %}"${{aws_secrets:credential-secret-config:username}}"{% endraw %} + password: {% raw %}"${{aws_secrets:credential-secret-config:password}}"{% endraw %} index: "test-migration" ``` diff --git a/_query-dsl/full-text/match.md b/_query-dsl/full-text/match.md index 431ecc6a278..f0ae5d6c7bb 100644 --- a/_query-dsl/full-text/match.md +++ b/_query-dsl/full-text/match.md @@ -8,7 +8,7 @@ nav_order: 10 # Match query -Use the `match` query for full-text search on a specific document field. If you run a `match` query on a [`text`]({{site.url}}/{{site.baseurl}}/field-types/supported-field-types/text/) field, the `match` query [analyzes]({{site.url}}/{{site.baseurl}}/analyzers/index/) the provided search string and returns documents that match any of the string's terms. If you run a `match` query on an exact-value field, it returns documents that match the exact value. The preferred way to search exact-value fields is to use a filter because, unlike a query, a filter is cached. +Use the `match` query for full-text search on a specific document field. If you run a `match` query on a [`text`]({{site.url}}{{site.baseurl}}/field-types/supported-field-types/text/) field, the `match` query [analyzes]({{site.url}}{{site.baseurl}}/analyzers/index/) the provided search string and returns documents that match any of the string's terms. If you run a `match` query on an exact-value field, it returns documents that match the exact value. The preferred way to search exact-value fields is to use a filter because, unlike a query, a filter is cached. The following example shows a basic `match` query for the word `wind` in the `title`: