@intentius/chant-lexicon-azure 0.24.0 → 0.26.0

package/src/spec/api-versions.test.ts

@@ -38,13 +38,30 @@ describe("compareApiDates", () => {
 
 describe("latestVersionPerProvider", () => {
   it("picks the latest API version per provider", () => {
+    // Providers with no PROVIDER_VERSION_OVERRIDES entry — Microsoft.Compute
+    // and Microsoft.Authorization are pinned (#1144, #223) and covered by
+    // their own describe block below.
     const paths = [
       "schemas/2022-01-01/Microsoft.Storage.json",
       "schemas/2023-06-01/Microsoft.Storage.json",
-      "schemas/2023-01-01/Microsoft.Compute.json",
+      "schemas/2023-01-01/Microsoft.Network.json",
     ];
     const result = latestVersionPerProvider(paths);
     expect(result.get("Microsoft.Storage")?.apiVersion).toBe("2023-06-01");
-    expect(result.get("Microsoft.Compute")?.apiVersion).toBe("2023-01-01");
+    expect(result.get("Microsoft.Network")?.apiVersion).toBe("2023-01-01");
+  });
+});
+
+describe("PROVIDER_VERSION_OVERRIDES", () => {
+  it("pins Microsoft.Compute to the last date with the virtualMachines family (#1144)", () => {
+    const paths = [
+      "schemas/2025-11-01/Microsoft.Compute.json",
+      "schemas/2026-03-01/Microsoft.Compute.json",
+      "schemas/2026-03-02/Microsoft.Compute.json",
+    ];
+    const result = latestVersionPerProvider(paths);
+    // 2026-03-02 is the naive "latest by date" but drops virtualMachines
+    // (a disk-only delta); the override keeps 2026-03-01 instead.
+    expect(result.get("Microsoft.Compute")?.apiVersion).toBe("2026-03-01");
   });
 });

package/src/spec/api-versions.ts

@@ -53,9 +53,21 @@ export function parseSchemaPath(
  * includes the plain `roleAssignments` / `roleDefinitions` resources; they live
  * in 2022-04-01, the latest stable that still has them. Pin it so those
  * generate (the naming table maps both). See #223.
+ *
+ * Microsoft.Compute has the same issue (#1144): at the schema commit pinned
+ * in ../spec/fetch.ts, the newest dated `Microsoft.Compute.json` (2026-03-02)
+ * is a narrow disk-only delta that drops `virtualMachines`,
+ * `virtualMachineScaleSets`, and `availabilitySets` entirely — not a rename,
+ * an omission, since Azure alternates between a "VM flavor" and a "disk
+ * flavor" of this file across dates rather than publishing one cumulative
+ * file. 2026-03-01 is the most recent date that still has the VM family
+ * (validate.ts's REQUIRED_NAMES and composites/vm-linux.ts depend on it);
+ * it drops the disk-only resources (disks, diskAccesses, diskEncryptionSets,
+ * snapshots), which nothing here currently references.
  */
 export const PROVIDER_VERSION_OVERRIDES: Record<string, string> = {
   "Microsoft.Authorization": "2022-04-01",
+  "Microsoft.Compute": "2026-03-01",
 };
 
 /**

package/src/spec/fetch.ts

@@ -69,10 +69,42 @@ export interface ArmSchemaDefinition {
   items?: ArmSchemaProperty;
 }
 
-const TARBALL_URL =
-  "https://github.com/Azure/azure-resource-manager-schemas/archive/refs/heads/main.tar.gz";
+/**
+ * Pinned commit of Azure/azure-resource-manager-schemas (#1144).
+ *
+ * The repo has no tagged releases, so unlike gcp (`KCC_VERSION`) or k8s
+ * (`K8S_SCHEMA_VERSION`) there is no version tag to pin against — codegen
+ * used to fetch `refs/heads/main` directly. That meant a cold cache picked
+ * up whatever upstream state had landed since the cache last expired, while
+ * a warm cache kept serving whatever was current when it was last filled.
+ * Azure republishes per-provider schema files under new dates constantly,
+ * and a later date can drop resources an earlier one defined (see
+ * PROVIDER_VERSION_OVERRIDES in ./api-versions.ts) — so which resources
+ * even exist to generate depends on exactly when you fetch, not just what
+ * the fetch URL happens to be. That broke composites/vm-linux.ts at tsc
+ * nondeterministically, depending on which runner's cache was warm.
+ *
+ * Pinning to a commit SHA makes generation reproducible regardless of cache
+ * state. Bump policy: #523's scheduled lexicon-upgrade cron (rolling-spec
+ * bucket, sub-issue #526) is meant to propose bumps to this constant as a
+ * reviewable PR once built. Until then, bump by hand: take the current
+ * `main` HEAD sha from
+ * https://github.com/Azure/azure-resource-manager-schemas/commits/main,
+ * regenerate, fix up any composite left referencing a renamed or vanished
+ * export (adding a PROVIDER_VERSION_OVERRIDES entry if a resource dropped
+ * out of the naive "latest by date" pick), and update this constant +
+ * comment.
+ */
+export const AZURE_SCHEMA_COMMIT = "0085cb6f3a98e735359807143bcb1667aeec930f";
+
+const TARBALL_URL = `https://github.com/Azure/azure-resource-manager-schemas/archive/${AZURE_SCHEMA_COMMIT}.tar.gz`;
 const CACHE_DIR = join(homedir(), ".chant");
-const CACHE_FILE = join(CACHE_DIR, "azure-resource-manager-schemas.tar.gz");
+// The cache filename embeds the pin so a stale tarball from before a bump
+// can never mask the bump: restoring an old ~/.chant (e.g. a CI cache
+// partial-key fallback, or a developer's pre-existing cache) simply misses
+// this filename and re-downloads, instead of silently serving pre-bump
+// schemas under a name that still matches (#1144).
+const CACHE_FILE = join(CACHE_DIR, `azure-resource-manager-schemas-${AZURE_SCHEMA_COMMIT}.tar.gz`);
 
 /** Paths to skip (common-types, non-provider files). */
 function isProviderSchema(path: string): boolean {