Add support for DefaultAzureCredential in Azure Storage backend #451
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This change extends the Azure Storage (
ASFileSystem
) client initialization to supportDefaultAzureCredential
from the Azure Identity library.#include <azure/identity.hpp>
andnamespace ai = Azure::Identity;
.AZURE_USE_DEFAULT_CREDENTIAL
is set to"1"
or"true"
, theBlobServiceClient
is constructed usingDefaultAzureCredential
.account_key_
is provided, Shared Key authentication is used.BlobServiceClient
.This enables Triton to authenticate with Azure Storage using Managed Identity, environment-based credentials, or developer tools (VS/CLI), improving integration with Azure-hosted deployments.
Testing
Built and ran Triton inside a container with Azure SDK support enabled.
Inside container I was able to successfully run:
`
az login
tritonserver --model-repository=as://deeplearningstorage.blob.core.windows.net/model-repo
`