Update-TTKCache misses at least Microsoft.Resources/tags

[jimdigriz]

After running Update-TTKCache we still seem to be missing the latest version of Microsoft.Resources/tags (2024-03-01 is missing):

$ jq -a '."Microsoft.Resources/tags"' arm-ttk/arm-ttk/cache/AllAzureResources.cache.json
[
  {
    "aliases": null,
    "apiProfiles": null,
    "apiVersions": [
      "2023-07-01",
      "2022-09-01",
      "2019-10-01",
      "2019-05-01",
      "2019-04-01",
      "2019-03-01",
      "2018-11-01"
    ],
    "capabilities": "SupportsExtension",
    "defaultApiVersion": null,
    "locationMappings": null,
    "locations": [],
    "properties": null,
    "resourceType": "Microsoft.Resources/tags",
    "zoneMappings": null
  }
]

Other resources in that cache file have API versions even from 2024-08-XX-preview so something is up.

Using arm-ttk version 2024.03.28 - 0.25.

Let me know if you need anything else.

[jimdigriz]

Deeper down the rabbit hole I go...

Latest versions from differing Microsoft sources (ttk post running Update-TTKCache):

• Microsoft.Web/serverFarms:
  • ttk: 2023-12-01
  • doc: 2022-09-01
  • REST: 2023-12-01
• Microsoft.Resources/tags
  • ttk: 2023-07-01
  • doc: 2024-03-01
  • REST: 2024-08-01
• Microsoft.Compute/virtualMachines
  • ttk: 2024-07-01
  • doc: 2024-07-01
  • REST: 2024-07-01

From this it looks like:

• REST I am assuming is 'truth' and reflects the latest version available for a resource type
• Azure user documentation lags somewhat behind REST a little which is a bit unexpected, it would be helpful to release the docs before the API version and just state attempts to use an API version earlier than the date it represents is 'undefined' behaviour
• TTK, uses the output of az provider list which lags a little behind REST which I suppose is to be expected as API versions are region specific; as an example even nearly a year later there is a warning in regards to interacting with IMDS

The problem here is TTK is beating up its userbase on in-actionable items, such as how can I fix Microsoft.Web/serverFarms when there is no documentation for that API version?

What is the actionable solution here for the user facing these error messages?