Each component of the pipeline should be responsible for persisting "sensitive" data

[michalpristas]

Component(s)

No response

Is your feature request related to a problem? Please describe.

followup to #31074

Each component of the pipeline should be responsible for persisting "sensitive" data upon failures, restarts etc.

Describe the solution you'd like

I look at this as a matter of stateful vs stateless components. Stateful components should persist their state during shutdown if a storage extension is available. There may be a case for formalizing a declaration of statefulness so that we can more easily enforce standards like this. e.g. Add a flag to consumer.Capabilities or metadata.yaml files.
@djaglowski

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.