Skip to content

Commit e5a9a24

Browse files
docs: correct lease vendor namespace wording (#89)
Co-authored-by: Nick Ficano <nficano@gmail.com>
1 parent a94e182 commit e5a9a24

1 file changed

Lines changed: 7 additions & 1 deletion

File tree

docs/guides/leases.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,14 +27,20 @@ patterns. Reserved capability names:
2727
| `cost.budget` | Spend cap; entries are `currency:amount` strings (see §9.6 below). |
2828

2929
Custom capability names MUST use `x-vendor.<vendor>.<cap>` (at least
30-
three dot-separated segments after the `x-vendor.` prefix):
30+
two dot-separated segments after the `x-vendor.` prefix). See the
31+
[vendor extensions guide](./vendor-extensions.md) for the canonical
32+
namespace rules:
3133

3234
```ts
3335
const lease = {
3436
"x-vendor.acme.kafka.publish": ["topic-events-*"],
3537
};
3638
```
3739

40+
For the same namespace shape in another ARCP surface, the tracing
41+
middleware uses `x-vendor.opentelemetry.tracecontext` as its envelope
42+
extension key.
43+
3844
## Example
3945

4046
```ts

0 commit comments

Comments
 (0)