From 0ea39b2d25342f68faacb2c9c64e4c5658e775ca Mon Sep 17 00:00:00 2001 From: Newbe36524 Date: Wed, 13 Mar 2024 17:19:38 +0800 Subject: [PATCH 1/6] Update secrets-scopes.md Signed-off-by: Newbe36524 --- .../building-blocks/secrets/secrets-scopes.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/secrets/secrets-scopes.md b/daprdocs/content/en/developing-applications/building-blocks/secrets/secrets-scopes.md index f76bfa3f3d2..167d85f986d 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/secrets/secrets-scopes.md +++ b/daprdocs/content/en/developing-applications/building-blocks/secrets/secrets-scopes.md @@ -4,7 +4,6 @@ title: "How To: Use secret scoping" linkTitle: "How To: Use secret scoping" weight: 3000 description: "Use scoping to limit the secrets that can be read by your application from secret stores" -type: docs --- Once you [configure a secret store for your application]({{< ref setup-secret-store >}}), *any* secret defined within that store is accessible by default from the Dapr application. @@ -107,4 +106,4 @@ Scenarios | defaultAccess | allowedSecrets | deniedSecrets | permission ## Related links - List of [secret stores]({{< ref supported-secret-stores.md >}}) -- Overview of [secret stores]({{< ref setup-secret-store.md >}}) \ No newline at end of file +- Overview of [secret stores]({{< ref setup-secret-store.md >}}) From 364e4821d7fd4c14a8c927c358269ab805a2101c Mon Sep 17 00:00:00 2001 From: Newbe36524 Date: Wed, 13 Mar 2024 17:20:50 +0800 Subject: [PATCH 2/6] Update gRPC-integration.md Signed-off-by: Newbe36524 --- .../en/developing-applications/integrations/gRPC-integration.md | 1 - 1 file changed, 1 deletion(-) diff --git a/daprdocs/content/en/developing-applications/integrations/gRPC-integration.md b/daprdocs/content/en/developing-applications/integrations/gRPC-integration.md index cd3380c972d..bdd4a7ab020 100644 --- a/daprdocs/content/en/developing-applications/integrations/gRPC-integration.md +++ b/daprdocs/content/en/developing-applications/integrations/gRPC-integration.md @@ -4,7 +4,6 @@ title: "How to: Use the gRPC interface in your Dapr application" linkTitle: "How to: gRPC interface" weight: 6000 description: "Use the Dapr gRPC API in your application" -type: docs --- Dapr implements both an HTTP and a gRPC API for local calls. [gRPC](https://grpc.io/) is useful for low-latency, high performance scenarios and has language integration using the proto clients. From 8da9af7624c6efdf65bcad7427d5fd858ae4e699 Mon Sep 17 00:00:00 2001 From: Newbe36524 Date: Wed, 13 Mar 2024 17:21:14 +0800 Subject: [PATCH 3/6] Update open-telemetry-collector-jaeger.md Signed-off-by: Newbe36524 --- .../tracing/otel-collector/open-telemetry-collector-jaeger.md | 1 - 1 file changed, 1 deletion(-) diff --git a/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md b/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md index 6ee6727beb5..98248d75502 100644 --- a/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md +++ b/daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md @@ -4,7 +4,6 @@ title: "Using OpenTelemetry Collector to collect traces to send to Jaeger" linkTitle: "Using the OpenTelemetry for Jaeger" weight: 1200 description: "How to push trace events to Jaeger distributed tracing platform, using the OpenTelemetry Collector." -type: docs --- While Dapr supports writing traces using OpenTelemetry (OTLP) and Zipkin protocols, Zipkin support for Jaeger has been deprecated in favor of OTLP. Although Jaeger supports OTLP directly, the recommended approach for production is to use the OpenTelemetry Collector to collect traces from Dapr and send them to Jaeger, allowing your application to quickly offload data and take advantage of features like retries, batching, and encryption. For more information, read the Open Telemetry Collector [documentation](https://opentelemetry.io/docs/collector/#when-to-use-a-collector). From 75388c2812bcba4dc79ec0780c6dc273cf5478ff Mon Sep 17 00:00:00 2001 From: Newbe36524 Date: Wed, 13 Mar 2024 17:21:31 +0800 Subject: [PATCH 4/6] Update zipkin.md Signed-off-by: Newbe36524 --- daprdocs/content/en/operations/observability/tracing/zipkin.md | 1 - 1 file changed, 1 deletion(-) diff --git a/daprdocs/content/en/operations/observability/tracing/zipkin.md b/daprdocs/content/en/operations/observability/tracing/zipkin.md index 23ecfd312f3..6235100d4b6 100644 --- a/daprdocs/content/en/operations/observability/tracing/zipkin.md +++ b/daprdocs/content/en/operations/observability/tracing/zipkin.md @@ -4,7 +4,6 @@ title: "How-To: Set up Zipkin for distributed tracing" linkTitle: "Zipkin" weight: 4000 description: "Set up Zipkin for distributed tracing" -type: docs --- ## Configure self hosted mode From e5d372f1a3483650bb9d8e7f7a0df02070cf7a2b Mon Sep 17 00:00:00 2001 From: Newbe36524 Date: Wed, 13 Mar 2024 17:21:54 +0800 Subject: [PATCH 5/6] Update kubernetes-job.md Signed-off-by: Newbe36524 --- .../content/en/operations/hosting/kubernetes/kubernetes-job.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-job.md b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-job.md index bd8c8f5eff5..e4aebbbbb15 100644 --- a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-job.md +++ b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-job.md @@ -4,7 +4,6 @@ title: "Running Dapr with a Kubernetes Job" linkTitle: "Kubernetes Jobs" weight: 70000 description: "Use Dapr API in a Kubernetes Job context" -type: docs --- The Dapr sidecar is designed to be a long running process. In the context of a [Kubernetes Job](https://kubernetes.io/docs/concepts/workloads/controllers/job/) this behavior can block your job completion. @@ -67,4 +66,4 @@ func main() { ## Related links - [Deploy Dapr on Kubernetes]({{< ref kubernetes-deploy.md >}}) -- [Upgrade Dapr on Kubernetes]({{< ref kubernetes-upgrade.md >}}) \ No newline at end of file +- [Upgrade Dapr on Kubernetes]({{< ref kubernetes-upgrade.md >}}) From 7cd5f7e69a5c1efded3a61fd5884acfc23eb9df3 Mon Sep 17 00:00:00 2001 From: Newbe36524 Date: Wed, 13 Mar 2024 17:22:17 +0800 Subject: [PATCH 6/6] Update middleware-bearer.md Signed-off-by: Newbe36524 --- .../supported-middleware/middleware-bearer.md | 1 - 1 file changed, 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-bearer.md b/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-bearer.md index d47c769a93b..eb9689bc5d3 100644 --- a/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-bearer.md +++ b/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-bearer.md @@ -3,7 +3,6 @@ type: docs title: "Bearer" linkTitle: "Bearer" description: "Use bearer middleware to secure HTTP endpoints by verifying bearer tokens" -type: docs aliases: - /developing-applications/middleware/supported-middleware/middleware-bearer/ ---