RepoJournal
HashiCorp @hashicorp
176 wires and counting

$ follow HashiCorp

Keep up with HashiCorp in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-08-19
stories 39
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

AZURERM ROLE ASSIGNMENTS GO IN-PLACE

By RepoJournal · Filed · About HashiCorp · Composed from the cited sources · methodology

pl4nty magodo katbyte Ruben Nic jonathanfrappier mister-ken dependabot
7 people shipped this
pl4nty @pl4nty 1 cited magodo @magodo 1 cited katbyte @katbyte 1 cited Ruben Nic @RubenSandwich 1 cited jonathanfrappier @jonathanfrappier 1 cited mister-ken @mister-ken 1 cited dependabot @dependabot

Terraform's Azure provider just made role assignments updatable in place, cutting out the delete-and-recreate dance for conditions and descriptions.

The headline change lands in terraform-provider-azurerm: `azurerm_role_assignment` now supports in-place updates for `condition`, `condition_version`, and `description` [1], a long-awaited fix that eliminates the need to destroy and recreate role assignments for routine edits. The provider also gained a documentation clarification for `azurerm_cdn_endpoint` [2], which may prevent misconfigurations now that compression settings are properly documented. On the quality front, a linter sweep enabled four tfproviderlint checks and burned down 373 existing violations [3], with more checks expected in subsequent PRs. Meanwhile, the web-unified-docs desk clarified that Vault Radar can only be enabled in one project per HCP organization [4], and moved external Vault Kubernetes integration guidance from tutorial to docs [5]. Across the 24 commits and 15 PRs, the only security-adjacent item is a workflow comment cleanup in build-pr-preview.yml [6], which doesn't change behavior. For Azure users, this is the upgrade you've been waiting for, but it's still in the PR pipeline, so watch for the release.

Action items

References

  1. [1] `azurerm_role_assignment` - Support update for `description`, `condition` and `condition_version` ↗ hashicorp/terraform-provider-azurerm
  2. [2] docs: `azurerm_cdn_endpoint` requires `content_types_to_compress` if `is_compression_enabled` ↗ hashicorp/terraform-provider-azurerm
  3. [3] linters - enable tfproviderlint checks 1/5 - Services a–c (apimanagement … customproviders, incl. compute, containers, cosmos, batch) + legacy + shared validation helpers ↗ hashicorp/terraform-provider-azurerm
  4. [4] Update Vault Radar project enablement information (#3133) hashicorp/web-unified-docs ↗
  5. [5] kak/external-vault/ moving some of this info over to docs - external vault with agent inj… ↗ hashicorp/web-unified-docs
  6. [6] Clarify security checks in build-pr-preview.yml (#3108) hashicorp/web-unified-docs ↗

$ ls hashicorp/reviews/ # the step-back reads

the week in review Consul provider patches two Go CVEs, adds 2.23.0 upgrade gate the month in review Consul patches four CVEs as Go bumps sweep repos
Full archive → Weekly reviews →

Quick answers

What shipped in HashiCorp on August 19, 2026?
Terraform's Azure provider just made role assignments updatable in place, cutting out the delete-and-recreate dance for conditions and descriptions. In total, 24 commits and 15 pull requests landed.
Who contributed to HashiCorp on August 19, 2026?
7 developers shipped this update, including dependabot, pl4nty, magodo, katbyte, Ruben Nic, jonathanfrappier, and mister-ken.
What were the notable HashiCorp updates?
`azurerm_role_assignment` - Support update for `description`, `condition` and `condition_version`, docs: `azurerm_cdn_endpoint` requires `content_types_to_compress` if `is_compression_enabled`, and linters - enable tfproviderlint checks 1/5 - Services a–c (apimanagement … customproviders, incl. compute, containers, cosmos, batch) + legacy + shared validation helpers.
♥

$ log @hashicorp --recent

A copyright sweep is the whole day 2 shipped HashiCorp: no material update 2 shipped Application Design Center lands, workload identity pools grow two fields 46 shipped Consul CI breaks on jq 1.8 as Ubuntu 26.04 runners arrive 31 shipped

$ log --all # elsewhere on the wire

Agent Security Quiet day in agent security as guard coverage reaches four clients Alignment & Post-training verl defaults Ascend RL mode, open-instruct unblocks SFT packing

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.