Skip to content

[Storage] DataLakePathClient APIs are not creating scopes when being called directly #38567

Open
@amnguye

Description

@amnguye

Currently our DataLakePathClient tests are being tested through calling it's derived clients (e.g. DataLakeFileClient and DataLakeDirectoryClient). And when being called directly you would get a no scope detected error.

This was probably done intentionally not to accidentally create a double scope. However I think the correct way to go about this is to create the scope in the PathClient and pass the resource scope name to the PathClient, instead of starting it in the FileClient and DirectoryClient.

Metadata

Metadata

Assignees

Labels

ClientThis issue points to a problem in the data-plane of the library.StorageStorage Service (Queues, Blobs, Files)bugThis issue requires a change to an existing behavior in the product in order to be resolved.test-reliabilityIssue that causes tests to be unreliable

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions