$ the-wire · showcase
29 CIS GCP v5.0.0 policies land, Azure phase two follows
By RepoJournal · Filed · About HashiCorp · Composed from the cited sources · methodology
10 people shipped this
KristinLBradley
@KristinLBradley
1 cited
annawanggg
@annawanggg
1 cited
TIMMAREDDY DEEKSHITHA
@DeekshithaTimmareddy
1 cited
Divyansh Singh
@hashi-divyansh
1 cited
panman90
@panman90
1 cited
didoo
@didoo
dchyun
@dchyun
LincyBainiwal
@LincyBainiwal
HerambLimaye
@HerambLimaye
Anubhav Goel
@anubhav-goel
The prewritten policy library absorbed its widest single-day expansion, with 29 CIS GCP v5.0.0 controls plus Azure phase-two and IAM/monitoring policy sets, while the design system fixed an accessibility DOM order bug that touches every Radio, Checkbox, and Toggle.
feat(gcp): add 29 CIS GCP v5.0.0 policies (#76) hashicorp/prewritten-terraform-policy-library
Twenty-nine policies, tests, and docs for CIS GCP Foundations Benchmark v5.0.0 spanning IAM, Compute, Storage, Cloud SQL, BigQuery, and Dataproc. Cloud SQL TLS, authorized-network, and database-flag checks also cover destinations created by Database Migration Service profiles, and control 7.2 applies a dataset default CMEK only to newly created datasets.
`FormField` - Fix DOM order of input and label for flag layout (HDS-6781) hashicorp/design-system
Pulls into your Terraform plans a phase-two Azure policy set with tests and documentation, including fixes scoping SQL firewall alerts to SQL resources and aligning Key Vault RBAC schema support. The Bastion policy was pulled as unenforceable, so anything relying on it needs another control.
feat(azure): add ten IAM and monitoring policies with tests and docs (#65) hashicorp/prewritten-terraform-policy-library
Ten more Azure IAM and monitoring policies land with tests and docs; a security defaults policy was dropped because it depended on an unapproved provider. Plan-based scope limitations are now documented alongside the checks, which matters if you gate applies on policy results.
`CodeBlock` - Fix incorrect placement of sr-only highlight markers when `@lineNumberStart` is defined hashicorp/design-system
The sr-only "highlight start" and "highlight end" markers drifted onto the wrong lines whenever @lineNumberStart was set, because the offset never accounted for 1-based numbering and was not subtracted from the multi-line highlight end. Screen reader users tracking highlighted code now get the right line.
Mansi dns bug fix (#1333) hashicorp/consul-dataplane
A DNS fix lands in consul-dataplane with tests and unused code removed during review. A 2.1.0-rc2 changelog backport to main was merged separately, with no dependency or Envoy changes on the point-release branch.
