Skip to content

[FEATURE REQ] Ability to traverse blob hierarchy upwards. BlobClient->BlobContainer #16359

Closed

Description

Library or service name.
Azure.Storage.Blobs

Is your feature request related to a problem? Please describe.
While working on Storage Webjobs Extension migration from V11 to V12 I keep finding places where original authors leveraged ability to traverse hierarchy upwards. I.e. jump from BlobClient to Container client (and to service client). To make it work with V12 I often had to pass higher level client along with lower level client or magically resolve creds or higher level client from some "context".
A recent example of such pain is in #16336 where in order to jump from BlockBlobClient to BlobClient and vice versa requires magic. Ideally I should be able to write blockBlobClient.GetContainerClient().GetBlobClient(blockBlobClient.Name).
Additionally the blobClients already have ContainerName property, so information about parent is available. But if someone doesn't have reference to higher level client handy then they're facing quite a refactoring as there's no good way to transfer pipeline and credential from one blobClient to other blobClient.

Adding such capability might ease a lot of migration pains.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    ClientThis issue points to a problem in the data-plane of the library.StorageStorage Service (Queues, Blobs, Files)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions