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

Client side encryption: ability to define a client encryption key using IaC #4891

Open
tsbala opened this issue Nov 14, 2024 · 0 comments
Open

Comments

@tsbala
Copy link

tsbala commented Nov 14, 2024

Is your feature request related to a problem? Please describe.
We have a situation where we are not able to define a client encryption key on a container because the container has been created using Pulumi (IaC tool) and it is not possible for us to generate a client side encryption key using Azure REST API. The creation of Azure resource is managed by a different team and it is not possible to include Azure SDK calls to generate the client encryption key.

Describe the solution you'd like
Two possible solutions

  • Allow patch on an existing container to add a client encryption key. Happy for the patch to fail if the container has data in it.
  • Allow creation of client side encryption key using Azure REST API
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants