Tracking issue for `configoptional.AddEnabledField` feature gate

[mx-psi]

trafficstars

Feature gate name

configoptional.AddEnabledField

Description

Allows to configure any field using a configoptional.Optional with enabled. For example, the following configuration becomes valid:

receivers:
  otlp:
    protocols:
      grpc:
        enabled: true

exporters:
  nop:

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [nop]

and is equivalent to:

receivers:
  otlp:
    protocols:
      grpc:

exporters:
  nop:

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [nop]

which also remains a valid way of configuring this.

Issues blocking alpha to beta transition

• [x] Get usage testing for the use cases we currently have in mind:
  • [x] confighttp keepalives,
  • [x] confighttp Cookies section (PoC)
  • [x] exportehelper batching from elasticsearchexporter and datadogexporter

Issues blocking beta to stable transition

• [ ] Make sure that dependent products (e.g. OpenTelemetry Helm Chart) can work correctly after this change
• [ ] Use configoptional for existing configuration sections that have an enabled field

History

Version	Status	PR
v1.45.0/v0.139.0	Introduced at alpha level	TBD

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}