Azure / Azure/azure-cli

az storage blob list --include option: (d) tag conflict between deleted and deletedwithversions

Open
#32,223 1 comment 1 reaction 2 assignees Claimed by @calvinhzy View on GitHub
act-codegen-extensibility-squad Auto-Assign Azure CLI Team customer-reported question Storage
Dominant language
Python
Stars
4.6k
Forks
3.5k
Avg merge
3d 2h
Merged PRs (30d)
60

Description

### Describe the bug

The --include option uses short tags for datasets, like (d)eleted.
However, both deleted and deletedwithversions use the same tag (d).

Because of this, it’s not possible to select deletedwithversions — the command always treats (d) as deleted.

### Related command

az storage blob list --include d

### Errors

No actual error message.
The command runs, but (d) is always interpreted as deleted, not deletedwithversions.

### Issue script & Debug output

Command use `az storage blob list --include (d)`

### Expected behavior

Each include option should have its own unique tag. (d) should only represent deleted, and deletedwithversions should have a different tag. This would let users include deletedwithversions without any conflict.

### Environment Summary

azure-cli 2.77.0

core 2.77.0
telemetry 1.1.0

Dependencies:
msal 1.34.0b1
azure-mgmt-resource 23.3.0

### Additional context

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.