You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Many users want to configure credentials at the resource level rather than creating a credential and entrusting it to Prefect. For example, we commonly see that Azure KeyVault is used to store secrets and users prefer to only have their secrets stored in one place, so enabling these blocks to function without storing secret values in Prefect is important.
Make it possible to use blob_storage_download, blob_storage_upload, blob_storage_list and other Azure Storage interactions without storing credentials or secrets in Prefect.
The text was updated successfully, but these errors were encountered:
taylor-curran
changed the title
Make the credentials optional for AzureBlobStorageCredentials or for Blob interaction.
Make the credentials optional for the AzureBlobStorageCredentials Block or for blob interaction in general.
Jan 25, 2023
Many users want to configure credentials at the resource level rather than creating a credential and entrusting it to Prefect. For example, we commonly see that Azure KeyVault is used to store secrets and users prefer to only have their secrets stored in one place, so enabling these blocks to function without storing secret values in Prefect is important.
Related to #68.
Make it possible to use
blob_storage_download
,blob_storage_upload
,blob_storage_list
and other Azure Storage interactions without storing credentials or secrets in Prefect.The text was updated successfully, but these errors were encountered: