[chore] Move deployment attributes to the registry

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -27,6 +27,7 @@ body:
         - area:code
         - area:container
         - area:db
+        - area:deployment
         - area:destination
         - area:device
         - area:disk

.github/ISSUE_TEMPLATE/change_proposal.yaml

@@ -20,6 +20,7 @@ body:
         - area:code
         - area:container
         - area:db
+        - area:deployment
         - area:destination
         - area:device
         - area:disk

.github/ISSUE_TEMPLATE/new-conventions.yaml

@@ -29,6 +29,7 @@ body:
         - area:code
         - area:container
         - area:db
+        - area:deployment
         - area:destination
         - area:device
         - area:disk

docs/attributes-registry/README.md

@@ -35,6 +35,7 @@ Currently, the following namespaces exist:
 * [Code](code.md)
 * [Container](container.md)
 * [DB](db.md) (database)
+* [Deployment](deployment.md)
 * [Destination](destination.md)
 * [Device](device.md)
 * [Disk](disk.md)

docs/attributes-registry/deployment.md

@@ -0,0 +1,16 @@
+# Deployment
+
+## Deployment Attributes
+<!-- semconv registry.deployment(omit_requirement_level) -->
+| Attribute  | Type | Description  | Examples  |
+|---|---|---|---|
+| `deployment.environment` | string | Name of the [deployment environment](https://wikipedia.org/wiki/Deployment_environment) (aka deployment tier). [1] | `staging`; `production` |
+
+**[1]:** `deployment.environment` does not affect the uniqueness constraints defined through
+the `service.namespace`, `service.name` and `service.instance.id` resource attributes.
+This implies that resources carrying the following attribute combinations MUST be
+considered to be identifying the same service:
+
+* `service.name=frontend`, `deployment.environment=production`
+* `service.name=frontend`, `deployment.environment=staging`.
+<!-- endsemconv -->

docs/resource/deployment-environment.md

@@ -9,7 +9,7 @@
 <!-- semconv deployment -->
 | Attribute  | Type | Description  | Examples  | Requirement Level |
 |---|---|---|---|---|
-| `deployment.environment` | string | Name of the [deployment environment](https://wikipedia.org/wiki/Deployment_environment) (aka deployment tier). [1] | `staging`; `production` | Recommended |
+| [`deployment.environment`](../attributes-registry/deployment.md) | string | Name of the [deployment environment](https://wikipedia.org/wiki/Deployment_environment) (aka deployment tier). [1] | `staging`; `production` | Recommended |
 
 **[1]:** `deployment.environment` does not affect the uniqueness constraints defined through
 the `service.namespace`, `service.name` and `service.instance.id` resource attributes.

model/registry/deployment.yaml

@@ -0,0 +1,22 @@
+groups:
+  - id: registry.deployment
+    prefix: deployment
+    type: attribute_group
+    brief: >
+     This document defines attributes for software deployments.
+    attributes:
+      - id: environment
+        type: string
+        stability: experimental
+        brief: >
+          Name of the [deployment environment](https://wikipedia.org/wiki/Deployment_environment)
+          (aka deployment tier).
+        note: |
+          `deployment.environment` does not affect the uniqueness constraints defined through
+          the `service.namespace`, `service.name` and `service.instance.id` resource attributes.
+          This implies that resources carrying the following attribute combinations MUST be
+          considered to be identifying the same service:
+
+          * `service.name=frontend`, `deployment.environment=production`
+          * `service.name=frontend`, `deployment.environment=staging`.
+        examples: ['staging', 'production']

model/resource/deployment_environment.yaml

@@ -1,22 +1,8 @@
 groups:
   - id: deployment
-    prefix: deployment
     type: resource
     brief: >
       The software deployment.
     attributes:
-      - id: environment
-        type: string
-        stability: experimental
-        brief: >
-          Name of the [deployment environment](https://wikipedia.org/wiki/Deployment_environment)
-          (aka deployment tier).
-        note: |
-          `deployment.environment` does not affect the uniqueness constraints defined through
-          the `service.namespace`, `service.name` and `service.instance.id` resource attributes.
-          This implies that resources carrying the following attribute combinations MUST be
-          considered to be identifying the same service:
-
-          * `service.name=frontend`, `deployment.environment=production`
-          * `service.name=frontend`, `deployment.environment=staging`.
-        examples: ['staging', 'production']
+      - ref: deployment.environment
+        requirement_level: recommended