Azurerm burns linter violations, Nomad command overhaul leads quiet week

The sharpest signal of the week came from terraform-provider-azurerm, where maintainers enabled the fourth batch of tfproviderlint checks across services from o through s, including storage, springcloud, and servicebus. That pass eliminated 373 linter violations, the kind of debt payoff that makes future changes faster to review and less likely to ship stale patterns. [1]

The Azure provider also added two meaningful capabilities. A common eventual consistency poller landed, giving resource handlers one shared way to wait for API convergence instead of each writing its own loop. [2] At the same time, the provider bumped Microsoft.Sql API packages from `2023-08-01-preview` to `2025-01-01`, a breaking change in the underlying API surface that will surface as new fields and changed defaults for SQL resources. [3] New resources arrived too: `azurerm_playwright_workspace` and identity/list support for `azurerm_cognitive_deployment`. [4][5]

Nomad's command overhaul led a quieter HashiCorp day, with changes aimed at reducing pointer boilerplate across the codebase, a refactor many Go codebases face when nullability conventions shift. Terraform's CLI now shows a token TTL warning message on login, a small but user-visible signal that tells operators when their token will expire without forcing them to dig through config. [6]

Across HashiCorp core libraries, dependency bumps rolled through the go group, updating go-getter and memberlist among others. [7][8] Nightly snapshots began shipping for nomad-driver-podman and nomad-pack, giving operators a faster path to test upcoming behavior. For once, no security advisories or breaking language changes dominated the conversation; the week was about grinding down technical debt and shipping incremental capabilities.