Abhinav 154e8736a5 Support managed OpenTelemetry metadata and PEM client identities (#57658) ...

## Why

Managed OpenTelemetry requirements could not specify span attributes or tracestate metadata.

## What changed

- Accept `otel.span_attributes` and `otel.tracestate` in requirements, merge them by attribute or member field, and expose them through app-server configuration and requirements reads.
- Protect required entries and their ancestors from configuration writes while preserving unmanaged sibling values and their origins. For example, requiring `otel.tracestate.vendor.tenant` leaves `vendor.region` writable. Empty metadata maps impose no requirements.
- Select Rustls when configuring an OTLP HTTP client certificate and private key so PEM client identities are accepted.

## Testing

Add coverage for metadata precedence, effective configuration, field-level write protection, and preservation of unmanaged values. Add blocking and asynchronous HTTP client construction tests using generated PEM certificates and keys.

GitOrigin-RevId: ada6000cc5e575b9a33451ec4aa58b6686dc20f7

2026-10-28 06:24:24 +00:00

..

examples

Add remote thread config loader protos (#18892)

2026-04-23 10:06:05 -07:00

scripts

Add remote thread config loader protos (#18892)

2026-04-23 10:06:05 -07:00

src

Support managed OpenTelemetry metadata and PEM client identities (#57658)

2026-10-28 06:24:24 +00:00

BUILD.bazel

Embed defaults in the packaged config layer (#38179)

2026-08-12 12:15:47 +00:00

Cargo.toml

Support managed OpenTelemetry configuration requirements (#57649)

2026-10-28 05:11:45 +00:00

defaults.toml

Make environment context date and timezone configurable (#52164)

2026-10-08 16:27:10 +00:00