How to configure an Expectation store in Azure blob storage

This article is for comments to: https://docs.greatexpectations.io/en/latest/how_to_guides/configuring_metadata_stores/how_to_configure_an_expectation_store_in_azure_blob_storage.html

Please comment +1 if this How to is important to you.

2 Likes

Let us know if this is important to you!

1 Like

Hi Kyle, is this still not implemented and therefore not possible with current version of Great Expectations?

@RomanAguilar This feature was actually just merged today (see [FEATURE] Add TupleAzureBlobStoreBackend: Support Azure Blob Storage as a backend store by syahdeini · Pull Request #1975 · great-expectations/great_expectations · GitHub) and should be in an official release in the next week or so. Feel free to test it out on the develop branch and let us know in Slack what you think. We’d also appreciate an update to the documentation here!

Would be nice to be able to authenticate with a Service Principal (TENANT ID, CLIENT ID, and CLIENT SECRET) and read these from Key Vault, as eg. here: config secrets integration