Certify Azure Table Storage as Stable in state store

[artursouza]

Describe the feature

Certify Azure Table Storage as GA in state store

Release Note

RELEASE NOTE:

[tanvigour]

/assign

[tanvigour]

Test Plan Draft

Proposed tests (Integration)

• Test for handling of existing table name vs new table
• Test for authentication using Azure auth layer : Update all other Azure components to use the common auth layer (and support Azure AD auth) #1103
• Test for consistency in behavior of Partition key and Row key with non-Dapr consumers
• Test for data persistence : write with dapr and read natively should have consistent data (data validation)
• Test for special error handling and negative test case conditions

[berndverst]

@tanvigour @artursouza important update:

This component should switch to the new / current Track 2 SDK for Table Storage.

This SDK supports BOTH the Azure Table Storage (as part of a Storage Container) as well as the Cosmos DB Table API.

https://github.com/Azure/azure-sdk-for-go/tree/main/sdk/data/aztables

IMO we should not certify as stable this component using the existing outdated SDK

[berndverst]

From recent Discord activity is clear that customers expect this component to connect to both Azure Blobstorage Tables as well as Cosmos DB Tables API. That can be facilitated by using the new Track 2 SDK and exposing the relevant options as component metadata.

Tracking the Track 2 migration work separately at #1528

[tanvigour]

From recent Discord activity is clear that customers expect this component to connect to both Azure Blobstorage Tables as well as Cosmos DB Tables API. That can be facilitated by using the new Track 2 SDK and exposing the relevant options as component metadata.

Tracking the Track 2 migration work separately at #1528

Do we have an estimate on completion of migration of table storage state store to track 2 sdk?

[tanvigour]

Test Plan Draft

Basic Test for created table for CRUD operations:

1. Able to create and test connection.
2. Able to do set, fetch, delete.

Basic Test for non-created table for CRUD operations:

1. Able to create and test connection.
2. Able to do set, fetch, delete data.
3. Delete the table

Test for authentication using Azure Auth layer

1. Save Data using Go SDK with already existing table
2. Retrieve data by using AAD credentials

[tanvigour]

@artursouza Please review the test plan when you get a chance. Thanks!

[mukundansundar]

@tanvigour

• Add tests for concurrency
• Add tests for etag support
• Test all CRUD operations ... as in add in tests for update and delete as well
• Add tests for the negative scenarios as well, like deleting or reading non-existent keys etc.