Added DeleteStateOnClear option to AzureStorage persistence provider.

[dbinky]

Added DeleteStateOnClear option to AzureStorage persistence provider.

• Added a boolean option to AzureBlobStorageOptions.cs for DeleteStateOnClear that defaults to true (which is the current, non-optional behavior)
• Added a check for the option in AzureBlobStorage.cs, allowing users to preserve cleared state blobs if desired
• Brings the AzureBlobStorage provider into conformance with the CosmosGrainStorage

Microsoft Reviewers: Open in CodeFlow

[dbinky]

@dotnet-policy-service agree

[ReubenBond]

If DeleteStateOnClear is false, is ClearStateAsync a no-op? I expect that it would write an empty blob if it's false.

[dbinky]

Yes, that's true. I could see this as useful in a few scenarios:
1 - It brings it into greater conformance with the Cosmos provider, which does have this option.
2 - I can envision some scenarios where it would be desirable to have the state blanked out and then saved. For example, if you're doing a synapse integration for analytics, just deleting the document from storage would not necessarily delete it from the synapse datalake, but if you wanted that data disincluded from your set, then saving and subsquently syncing a blank document would ensure that.
3 - There may be scenarios when you may not want to preserve the data of a document, but do want to have a record of used keys, which this would also do.