Fix required eTag conditional headers in Python

[Libba Lawrence (l0lawrence)]

Summary

• add an Azure HTTP scenario for a required If-Match header typed as Azure.Core.eTag
• verify the Python emitter exposes it as direct required if_match: str input while optional conditional headers retain etag + match_condition
• add sync and async runtime coverage and regenerate the scenario summary
• update the core submodule to Fix Python ETag preprocessing for nested operation groups microsoft/typespec#11964

Validation

• pnpm -r --filter "@azure-tools/azure-http-specs..." build
• TypeSpec Python emitter tests: 24 passed
• branded conditional-request sync/async tests: 10 passed
• core conditional-request sync/async tests: 10 passed

Depends on microsoft/typespec#11964.

[github-actions]

All changed packages have been documented.

• ✅ @azure-tools/azure-http-specs
• ✅ @azure-tools/typespec-python

Show changes

@azure-tools/azure-http-specs - internal ✏️

Add sync and async Python emitter coverage for a required If-Match header,> typed as Azure.Core.eTag.

@azure-tools/typespec-python - internal ✏️

Add sync and async Python emitter coverage for a required If-Match header,> typed as Azure.Core.eTag.

[github-actions]

📦 Package size report

✅ No notable package size changes compared to the base branch.

13 package(s) with no notable change

Package	Packed (base → head)	Δ Packed	Unpacked (base → head)	Δ Unpacked
@azure-tools/azure-http-specs	147.65 KB → 147.76 KB	+107 B (+0.1%)	1.16 MB → 1.17 MB	+1.04 KB (+0.1%)
@azure-tools/typespec-java	13.51 MB → 13.51 MB	-1 B (-0.0%)	15.04 MB → 15.04 MB	—
@azure-tools/typespec-autorest	81.22 KB → 81.22 KB	—	396.61 KB → 396.61 KB	—
@azure-tools/typespec-autorest-canonical	7.42 KB → 7.42 KB	—	26.00 KB → 26.00 KB	—
@azure-tools/typespec-azure-core	130.84 KB → 130.84 KB	—	709.83 KB → 709.83 KB	—
@azure-tools/typespec-azure-portal-core	42.48 KB → 42.48 KB	—	193.19 KB → 193.19 KB	—
@azure-tools/typespec-azure-resource-manager	182.94 KB → 182.94 KB	—	1.10 MB → 1.10 MB	—
@azure-tools/typespec-azure-rulesets	5.35 KB → 5.35 KB	—	33.04 KB → 33.04 KB	—
@azure-tools/typespec-client-generator-core	237.05 KB → 237.05 KB	—	1.27 MB → 1.27 MB	—
@azure-tools/typespec-go	263.50 KB → 263.50 KB	—	1.35 MB → 1.35 MB	—
@azure-tools/typespec-metadata	15.91 KB → 15.91 KB	—	62.26 KB → 62.26 KB	—
@azure-tools/typespec-python	42.21 KB → 42.21 KB	—	164.91 KB → 164.91 KB	—
@azure-tools/typespec-ts	540.90 KB → 540.90 KB	—	2.60 MB → 2.60 MB	—

_{Packed = gzipped .tgz published to npm. Unpacked = total extracted size. 🆕 added, 🗑️ removed. Packages from the core/ submodule are not included.
🔴 grew · 🟢 shrank — only changes of at least 512 B and 0.5% are marked.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@azure-tools/azure-http-specs@5477

npm i https://pkg.pr.new/@azure-tools/typespec-python@5477

commit: 9adeaca

[azure-sdk-automation]

You can try these changes here

🛝 Playground	🌐 Website

[Libba Lawrence (l0lawrence)]

Closing because the emitter fix will proceed without adding another Spector scenario in typespec-azure.