-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[QUERY] Possible to set WORM state on blob containers via .net API #24538
Comments
Thank you for your feedback. Tagging and routing to the team best able to assist. |
Hi @isobel-cullen, You can set WORM policies via the storage management plane SDK - https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/storage/Azure.ResourceManager.Storage A good example of how to do this is in our Immutable Storage with Versioning unit tests - azure-sdk-for-net/sdk/storage/Azure.Storage.Blobs/tests/ImmutableStorageWithVersioningTests.cs Line 36 in 7bc27aa
-Sean |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage. Issue DetailsQuery/Question Using Azure Blob Storage, is it possible to configure the immutability configuration of a container from the .NET client? Environment:
|
@seanmcc-msft Thank you, that is helpful. I cannot see a way to use a connection string with that client, am I missing something or does it not support Azurite? |
Unfortunately I do not work on that SDK. @blueww, do you have any insight? |
@isobel-cullen How to use SDK: https://azure.microsoft.com/da-dk/resources/samples/storage-dotnet-resource-provider-getting-started/ Set container level worm sample: azure-sdk-for-net/sdk/storage/Microsoft.Azure.Management.Storage/tests/Tests/BlobServiceTests.cs Line 507 in dc94a67
|
Please reopen if you have further questions. |
Query/Question
How can we help?
Using Azure Blob Storage, is it possible to configure the immutability configuration of a container from the .NET client?
Environment:
dotnet --info
output for .NET Core projects): .5.0.403The text was updated successfully, but these errors were encountered: