From 35ba19d3cb0e786f2b6c2f7e24118160b41c5ab2 Mon Sep 17 00:00:00 2001 From: Andreas Deininger Date: Tue, 9 Apr 2024 00:07:49 +0200 Subject: [PATCH] Docu: fix broken link (#5410) Fix broken link Co-authored-by: Scott Anderson --- .circleci/config.yml | 4 ++-- CONTRIBUTING.md | 2 +- .../v1/administration/configure/security/enable_tls.md | 2 +- .../write-data/best-practices/optimize-writes.md | 2 +- content/telegraf/v1/data_formats/input/json_v2.md | 7 ++++--- 5 files changed, 9 insertions(+), 8 deletions(-) diff --git a/.circleci/config.yml b/.circleci/config.yml index 556ee8200..e0ee7ca74 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -2,7 +2,7 @@ version: 2 jobs: build: docker: - - image: cimg/node:20.11.1 + - image: cimg/node:20.12.1 environment: S3DEPLOY_VERSION: "2.11.0" # From https://github.com/bep/s3deploy/releases @@ -49,7 +49,7 @@ jobs: deploy: docker: - - image: cimg/go:1.22.1 + - image: cimg/go:1.22.2 steps: - checkout - restore_cache: diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c40c52b05..aa8dbf62e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1195,7 +1195,7 @@ the content of the banner. {{< influxdbu >}} - + {{< influxdbu "influxdb-101" >}} diff --git a/content/enterprise_influxdb/v1/administration/configure/security/enable_tls.md b/content/enterprise_influxdb/v1/administration/configure/security/enable_tls.md index e61ffe566..cface4733 100644 --- a/content/enterprise_influxdb/v1/administration/configure/security/enable_tls.md +++ b/content/enterprise_influxdb/v1/administration/configure/security/enable_tls.md @@ -55,7 +55,7 @@ Regardless of your certificate's type, InfluxDB Enterprise supports certificates a private key file (`.key`) and a signed certificate file (`.crt`) file pair, as well as certificates that combine the private key file and the signed certificate file into a single bundled file (`.pem`). -In general, each node node should have its own certificate, whether signed or unsiged. +In general, each node node should have its own certificate, whether signed or unsigned. ## Set up HTTPS in an InfluxDB Enterprise cluster diff --git a/content/influxdb/cloud-dedicated/write-data/best-practices/optimize-writes.md b/content/influxdb/cloud-dedicated/write-data/best-practices/optimize-writes.md index 53a55cf5c..dbfd82ecd 100644 --- a/content/influxdb/cloud-dedicated/write-data/best-practices/optimize-writes.md +++ b/content/influxdb/cloud-dedicated/write-data/best-practices/optimize-writes.md @@ -203,7 +203,7 @@ EOF Replace the following: - {{% code-placeholder-key %}}`DATABASE_NAME`{{% /code-placeholder-key %}}: the name of the [database](/influxdb/cloud-dedicated/admin/databases/) to write data to - - {{% code-placeholder-key %}}`DATABASE_TOKEN`{{% /code-placeholder-key %}}: a [databse token](/influxdb/cloud-dedicated/admin/tokens/#database-tokens) with _write_ access to the specified database. + - {{% code-placeholder-key %}}`DATABASE_TOKEN`{{% /code-placeholder-key %}}: a [database token](/influxdb/cloud-dedicated/admin/tokens/#database-tokens) with _write_ access to the specified database. _Store this in a secret store or environment variable to avoid exposing the raw token string._ 2. To test the input and processor, enter the following command: diff --git a/content/telegraf/v1/data_formats/input/json_v2.md b/content/telegraf/v1/data_formats/input/json_v2.md index 5f06bd44e..269bc9f1f 100644 --- a/content/telegraf/v1/data_formats/input/json_v2.md +++ b/content/telegraf/v1/data_formats/input/json_v2.md @@ -156,7 +156,7 @@ file,title=The\ Lord\ Of\ The\ Rings author="Tolkien",random=2 ``` -You can find more complicated examples under the folder `testdata`. +You can find more complicated examples under the folder [`testdata`][] in the telegraf repo. ## Types @@ -165,7 +165,7 @@ The following rules are in place for this configuration: * If a type is explicitly defined, the parser will enforce this type and convert the data to the defined type if possible. If the type can't be converted then the parser will fail. -* If a type isn't defined, the parser will use the default type defined in the JSON (int, float, string) +* If a type isn't defined, the parser will use the default type defined in the JSON (int, float, string). The type values you can set: @@ -175,4 +175,5 @@ The type values you can set: * `float`, string values (with valid numbers) or integers can be converted to a float. * `bool`, the string values "true" or "false" (regardless of capitalization) or the integer values `0` or `1` can be turned to a bool. -[json]: https://www.json.org/ +[json]: https://www.json.org/ +[testdata]: https://github.com/influxdata/telegraf/tree/master/plugins/parsers/json_v2/testdata \ No newline at end of file