Skip to content

Feature request: Allow passing a valid context to encrypt/decrypt operations with AWS, Azure, GCP, PGP and HashiCorp Vault #1847

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

Open
matheuscscp opened this issue May 3, 2025 · 0 comments · May be fixed by #1848

Comments

@matheuscscp
Copy link
Contributor

matheuscscp commented May 3, 2025

Hi 👋

Right now we pass context.Background()/context.TODO() to the encrypt/decrypt operations internally. It would be valuable to accept a context in these operations and pass it down instead. As SDK users we'd like to do that in CNCF Flux. The SOPS CLI could also benefit from this passing a context tied to the SIGTERM and SIGINT signals.

@matheuscscp matheuscscp changed the title Feature request: Allow passing a valid context for encrypt/decrypt operations in AWS, Azure and GCP Feature request: Allow passing a valid context to encrypt/decrypt operations with AWS, Azure and GCP May 3, 2025
@matheuscscp matheuscscp changed the title Feature request: Allow passing a valid context to encrypt/decrypt operations with AWS, Azure and GCP Feature request: Allow passing a valid context to encrypt/decrypt operations with AWS, Azure, GCP, GnuPG and HashiCorp Vault May 3, 2025
@matheuscscp matheuscscp changed the title Feature request: Allow passing a valid context to encrypt/decrypt operations with AWS, Azure, GCP, GnuPG and HashiCorp Vault Feature request: Allow passing a valid context to encrypt/decrypt operations with AWS, Azure, GCP, PGP and HashiCorp Vault May 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant