From 51457754afe0b33eaefe2eea261c1398d09ff1b5 Mon Sep 17 00:00:00 2001 From: Carsten Lohmann Date: Mon, 24 Jan 2022 11:43:09 +0100 Subject: [PATCH] Apply minor documentation fixes. Signed-off-by: Carsten Lohmann --- site/documentation/content/admin-guide/common-config.md | 2 -- .../content/admin-guide/monitoring-tracing-config.md | 4 ++-- site/documentation/content/architecture/auth/index.md | 2 +- .../content/concepts/device-provisioning/index.md | 2 +- .../content/deployment/create-kubernetes-cluster.md | 2 +- 5 files changed, 5 insertions(+), 7 deletions(-) diff --git a/site/documentation/content/admin-guide/common-config.md b/site/documentation/content/admin-guide/common-config.md index ec5c763c58..ac5ad435ed 100644 --- a/site/documentation/content/admin-guide/common-config.md +++ b/site/documentation/content/admin-guide/common-config.md @@ -130,7 +130,6 @@ Note that the adapter uses a single cache for all responses from the service reg Consequently, the Credentials Service client configuration's *responseCacheMinSize* and *responseCacheMaxSize* properties determine the overall number of responses that can be cached. - ### Device Connection Service Connection Configuration {{% notice info %}} @@ -174,7 +173,6 @@ In general, the service supports all configuration properties of the [Infinispan Hotrod client](https://docs.jboss.org/infinispan/12.1/apidocs/org/infinispan/client/hotrod/configuration/package-summary.html#package.description) using `hono.deviceConnection` instead of the `infinispan.client.hotrod` prefix. - ### Command Router Service Connection Configuration {{% notice tip %}} diff --git a/site/documentation/content/admin-guide/monitoring-tracing-config.md b/site/documentation/content/admin-guide/monitoring-tracing-config.md index f1dfd3bc02..76cc0ebf43 100644 --- a/site/documentation/content/admin-guide/monitoring-tracing-config.md +++ b/site/documentation/content/admin-guide/monitoring-tracing-config.md @@ -32,11 +32,11 @@ system failure. ### Configuring a Metrics Back End -Hono uses [Micrometer](http://micrometer.io/) for providing metrics. It is +Hono uses [Micrometer](https://micrometer.io/) for providing metrics. It is possible to drop in any Micrometer compatible back end. Hono also uses the Micrometer integration with Spring Boot and Vert.x. -Please refer to the [Micrometer documentation](http://micrometer.io/docs) +Please refer to the [Micrometer documentation](https://micrometer.io/docs) for details regarding the configuration of a specific Micrometer back end. In most cases, you only need to add the back end specific jar files to the class path and add back end specific configuration properties to the `application.yml` file. diff --git a/site/documentation/content/architecture/auth/index.md b/site/documentation/content/architecture/auth/index.md index 23f65ef8d6..0d9ff892ea 100644 --- a/site/documentation/content/architecture/auth/index.md +++ b/site/documentation/content/architecture/auth/index.md @@ -45,7 +45,7 @@ The Apache Qpid Dispatch Router which is used in Hono's example deployment can b The identities and corresponding authorities that the *Auth Server* uses for verifying credentials and issuing tokens are defined in a configuration file (`services/auth/src/main/resources/permissions.json`) read in during start-up of the *Auth Server*. These authorities are used for authenticating and authorizing system components as well as *Business Applications*. -Please refer to the [Dispatch Router documentation](http://qpid.apache.org/components/dispatch-router/index.html) for details regarding configuration of *Dispatch Router* security. +Please refer to the [Dispatch Router documentation](https://qpid.apache.org/components/dispatch-router/index.html) for details regarding configuration of *Dispatch Router* security. ## Future Approach diff --git a/site/documentation/content/concepts/device-provisioning/index.md b/site/documentation/content/concepts/device-provisioning/index.md index a48e6c58fe..33d9551e9c 100644 --- a/site/documentation/content/concepts/device-provisioning/index.md +++ b/site/documentation/content/concepts/device-provisioning/index.md @@ -98,7 +98,7 @@ The provisioning is, of course, a one-time action, on subsequent connections the ## Automatic Gateway Provisioning Auto-provisioning of gateways involves the same steps as -[Automatic Device Provisioning]({{< ref "/concepts/device-provisioning#automatic-devicegateway-provisioning" >}}). +[Automatic Device Provisioning]({{< ref "/concepts/device-provisioning#automatic-device-provisioning" >}}). An extra attribute namely *auto-provision-as-gateway* is needed in the tenant's trusted CA configuration to enable auto-provisioning of gateways. If this attribute is set to `true` then the device registry provisions any unregistered devices that authenticate with a client certificate issued by this tenant's trusted CA as gateways, provided that the diff --git a/site/documentation/content/deployment/create-kubernetes-cluster.md b/site/documentation/content/deployment/create-kubernetes-cluster.md index a8313636d3..2f1a9505b4 100644 --- a/site/documentation/content/deployment/create-kubernetes-cluster.md +++ b/site/documentation/content/deployment/create-kubernetes-cluster.md @@ -66,7 +66,7 @@ This deployment model is not meant for productive use but rather for evaluation - An [Azure subscription](https://azure.microsoft.com/en-us/get-started/). - [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli) installed to setup the infrastructure. -- [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) and [helm](https://helm.sh/docs/using_helm/#installing-helm) +- [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) and [helm](https://helm.sh/docs/intro/install/) installed to deploy Hono into [Azure Kubernetes Service (AKS)](https://docs.microsoft.com/en-us/azure/aks/intro-kubernetes) ### Setup