$ the-wire · showcase
Boundary Helm charts add OpenShift support, provider maintenance continues
By RepoJournal · Filed · About HashiCorp · Composed from the cited sources · methodology
Both Boundary Helm charts gained OpenShift support this cycle, while the AWS and AzureRM Terraform providers saw test, drift-detection, and data source work rather than anything urgent.
Add OpenShift support to boundary-controller Helm chart hashicorp/boundary-controller-helm
The controller chart now omits fixed runAsUser and fsGroup when openshift.enabled=true so the SCC can assign a valid UID, and route.yaml creates an OpenShift Route while the API service is forced to ClusterIP. The deployment, db-init, db-migrate, db-repair, and bootstrap-admin manifests all follow that pattern, so existing non-OpenShift installs keep their current security context.
Icu 18817 backup hashicorp/boundary-worker-helm
The worker chart gets the same treatment via a new values.openshift.yaml, plus a Route for TCP passthrough to the worker proxy port. With OpenShift enabled, the proxy Service switches to ClusterIP and the Route carries external traffic, and the PVC storageClass becomes conditional so the cluster default can apply.
`azurerm_site_recovery_replicated_vm` - add caseInsensitiveProps to new `CustomDiffComputedSet` to avoid false-positive drift detection with IDs (#33424) hashicorp/terraform-provider-azurerm
azurerm_site_recovery_replicated_vm now compares managed_disk properties case-insensitively in CustomDiffComputedSet, ending false-positive drift reports caused by ID casing. If your plan has been showing spurious diffs on that resource, this is the fix.
Attributes added `data.express.route` - add support for `IPV6 + 1 attribute` hashicorp/terraform-provider-azurerm
Missing properties including ipv6 and microsoft_peering_config were added to the data.express.route data source's attributes. Configs reading those fields can now pull them from the data source instead of the resource.
GitHub Actions: Separates `tools` Go cache from code cache hashicorp/terraform-provider-aws
The AWS provider's GitHub Actions setup splits the tools Go cache from the code cache, which keeps tool-module churn from evicting build artifacts between runs. Elsewhere the provider did housekeeping: unused exports removed, tests added to fwtypes.AttributeTypes, and all aws_bedrockagentcore_registry acceptance tests deleted as technical debt.
