Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
michalpristas opened this issue Aug 15, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@michalpristas
Copy link
Contributor

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

@michalpristas michalpristas added enhancement New feature or request needs triage New item requiring triage labels Aug 15, 2024
@michalpristas michalpristas changed the title each component of the pipeline should be responsible for persisting "sensitive" data Each component of the pipeline should be responsible for persisting "sensitive" data Aug 15, 2024
@atoulme atoulme removed the needs triage New item requiring triage label Oct 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants