From 349be5a09816e8e44ea1ca2a42ba7a9d46ea1fdb Mon Sep 17 00:00:00 2001 From: Giovanni Liva Date: Thu, 2 Feb 2023 08:43:18 +0100 Subject: [PATCH] linting Signed-off-by: Giovanni Liva --- semantic_conventions/logs/log-deployment.yaml | 1 - semantic_conventions/trace/deployment.yaml | 2 +- specification/logs/semantic_conventions/deployment.md | 1 - specification/trace/semantic_conventions/deployment.md | 6 +++--- 4 files changed, 4 insertions(+), 6 deletions(-) diff --git a/semantic_conventions/logs/log-deployment.yaml b/semantic_conventions/logs/log-deployment.yaml index 5d64d651a4f..30576c9a3e5 100644 --- a/semantic_conventions/logs/log-deployment.yaml +++ b/semantic_conventions/logs/log-deployment.yaml @@ -34,4 +34,3 @@ groups: requirement_level: recommended - ref: deployment.task.name - ref: deployment.task.status - diff --git a/semantic_conventions/trace/deployment.yaml b/semantic_conventions/trace/deployment.yaml index 2fca46c2bd6..3807a1b83c3 100644 --- a/semantic_conventions/trace/deployment.yaml +++ b/semantic_conventions/trace/deployment.yaml @@ -83,7 +83,7 @@ groups: brief: 'The deployment was **not** completed correctly' - id: 'unknown' value: 'Unknown' - brief: 'The deployment wass unsuccessful and the reason is unknown' + brief: 'The deployment was unsuccessful and the reason is unknown' brief: > The status of the workload deployment. diff --git a/specification/logs/semantic_conventions/deployment.md b/specification/logs/semantic_conventions/deployment.md index 0578d0d8ce2..b7f6f3d9243 100644 --- a/specification/logs/semantic_conventions/deployment.md +++ b/specification/logs/semantic_conventions/deployment.md @@ -67,7 +67,6 @@ Task executions that support deployments SHOULD be recorded as attributes on the operations. Task executions MAY be recorded on "logs" or "events" depending on the context. - ### Attributes diff --git a/specification/trace/semantic_conventions/deployment.md b/specification/trace/semantic_conventions/deployment.md index 8b889808ecc..b4744521c1c 100644 --- a/specification/trace/semantic_conventions/deployment.md +++ b/specification/trace/semantic_conventions/deployment.md @@ -31,7 +31,7 @@ deployment of an application. ### Application -Each stage of the lifecycle of a cloud-native application deployment SHOULD be recorded as an Event on the span during +Each stage of the lifecycle of a cloud-native application deployment SHOULD be recorded as an Event on the span during which it occurred. @@ -54,7 +54,7 @@ The event name MUST be `deployment.application`. | `Unknown` | The deployment was unsuccessful and the reason is unknown | -### Workload +### Workload Cloud-native applications are composed of one or several components that are usually called [workloads](https://kubernetes.io/docs/concepts/workloads/). Similarly to applications, each stage of the lifecycle of a workload deployment SHOULD be recorded as an Event on the span during @@ -79,7 +79,7 @@ The event name MUST be `deployment.workload`. | `Progressing` | The deployment is currently taking place | | `Succeeded` | The deployment was completed correctly | | `Failed` | The deployment was **not** completed correctly | -| `Unknown` | The deployment wass unsuccessful and the reason is unknown | +| `Unknown` | The deployment was unsuccessful and the reason is unknown | ### Task