Azure / Azure/azure-rest-api-specs
[BUG] Azure Compute VM etag double escaped
Nobody has claimed this yet.
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 6k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 432
Description
API Spec link
API Spec version
2025-04-01
Describe the bug
Hi,
the etag in virtualmachine is double escaped.
Expected behavior
Should be:
"etag": "2",
Actual behavior
Current:
"etag": "\"2\"",
Reproduction Steps
Get any VM resource with a current api version (current stable as of this writing 2025-04-01)
az rest --method get --url "https://management.azure.com/subscriptions/xxxxxxxxxx/resourceGroups/xxxx/providers/Microsoft.Compute/virtualMachines/xxxx?api-version=2025-04-01"
Environment
current azure-cli (2.77.0)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the linked specification/compute/Compute.Management/VirtualMachine.tsp file and inspect the etag definition for API version 2025-04-01. Run the supplied az rest request against a VM, then confirm the specification change produces an etag value of "2" rather than the double-escaped value shown in the report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100