Skip to content
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

Improve diagnostics when an Azure endpoint is not configured. #4845

Merged
merged 1 commit into from
Apr 3, 2024

Conversation

teo-tsirpanis
Copy link
Member

@teo-tsirpanis teo-tsirpanis commented Apr 2, 2024

SC-43870

This PR changes the Azure VFS to fail with an explicit error if an operation on the Azure VFS was attempted, but an endpoint to Azure Blob Storage could not be determined based on the vfs.azure.storage_account_name and vfs.azure.blob_endpoint configuration options. The previous behavior was to emit a warning, which happened at the initialization of the VFS class if Azure is enabled, regardless of whether Azure is being actually used. That warning is no longer emitted.


TYPE: IMPROVEMENT
DESC: Improve diagnostics when an Azure endpoint is not configured.

Copy link

This pull request has been linked to Shortcut Story #43870: Remove azure warning when not using azure credentials.

@teo-tsirpanis teo-tsirpanis marked this pull request as ready for review April 3, 2024 11:51
Copy link
Contributor

@robertbindar robertbindar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Azure had to be compiled in to see this warning. This looks very much alright, thanks @teo-tsirpanis

@KiterLuc KiterLuc merged commit eefea1f into dev Apr 3, 2024
59 checks passed
@KiterLuc KiterLuc deleted the teo/azure-init-warning branch April 3, 2024 18:48
dudoslav pushed a commit that referenced this pull request Apr 17, 2024
[SC-43870](https://app.shortcut.com/tiledb-inc/story/43870/remove-azure-warning-when-not-using-azure-credentials)

This PR changes the Azure VFS to fail with an explicit error if an
operation on the Azure VFS was attempted, but an endpoint to Azure Blob
Storage could not be determined based on the
`vfs.azure.storage_account_name` and `vfs.azure.blob_endpoint`
configuration options. The previous behavior was to emit a warning,
which happened at the initialization of the VFS class if Azure is
enabled, regardless of whether Azure is being actually used. That
warning is no longer emitted.

---
TYPE: IMPROVEMENT
DESC: Improve diagnostics when an Azure endpoint is not configured.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants