RepoJournal
HashiCorp

@hashicorp

Terraform, Vault, Consul - infra-as-code for ops teams

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

One email a day. Unsubscribe in one click.

Pick a date

Topics: Go Infrastructure Full archive →

The Wire · Showcase

TERRAFORM GOOGLE PROVIDER LANDS APIGEE CREDENTIALS FIX AND NETWORK UPGRADES

By RepoJournal · Filed · About HashiCorp

The Terraform Google provider re-landed a critical Apigee feature that was reverted months ago, while simultaneously shipping network and artifact registry enhancements across both stable and beta channels.

The Apigee developer app credentials feature finally made it to production after a botched initial attempt. The first PR merged then reverted, leaving static consumer_key and consumer_secret unsupported on main for months [1]. The re-land fixes the original bug that caused the revert [1], and ships to both stable and beta channels [2] [1]. Separately, artifact registry got a meaningful win: upstream_credentials can now be updated in place instead of being immutable [3] [4], closing out a long-standing usability gap. On the networking front, two substantial features landed simultaneously: authzPolicy now supports networkRules [5] [6], and the network services agent gateway gained DNS peering configuration for cross-VPC DNS resolution [7] [8]. The compute layer is also getting refinement work, with several helper functions migrated from client library calls to direct HTTP [9] [10], reducing dependency bloat. Meanwhile, the Nomad ecosystem continues its nightly build cadence across nomad-driver-podman [11], nomad-autoscaler [12], and nomad-pack [13], keeping development moving on the orchestration side.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] apigee: add static consumer_key/consumer_secret to google_apigee_developer_app (re-land with fix) ↗ hashicorp/terraform-provider-google
  2. [2] apigee: add static consumer_key/consumer_secret to google_apigee_developer_app (re-land with fix) ↗ hashicorp/terraform-provider-google-beta
  3. [3] artifactregistry: Remove Immutable from upstream_credentials ↗ hashicorp/terraform-provider-google
  4. [4] artifactregistry: Remove Immutable from upstream_credentials ↗ hashicorp/terraform-provider-google-beta
  5. [5] feat: add support to networkRules on authzPolicy ↗ hashicorp/terraform-provider-google
  6. [6] feat: add support to networkRules on authzPolicy ↗ hashicorp/terraform-provider-google-beta
  7. [7] feat(networkservices): add DNS peering config to AgentGateway: ↗ hashicorp/terraform-provider-google
  8. [8] feat(networkservices): add DNS peering config to AgentGateway: ↗ hashicorp/terraform-provider-google-beta
  9. [9] Migrate , expandAliasIpRanges , expandAccessConfigs , expandIpv6AccessConfigs, expandNetworkInterfaces functions in compute_instance_helpers.go.tmpl to use direct HTTP rather than a client library ↗ hashicorp/terraform-provider-google
  10. [10] Migrate , expandAliasIpRanges , expandAccessConfigs , expandIpv6AccessConfigs, expandNetworkInterfaces functions in compute_instance_helpers.go.tmpl to use direct HTTP rather than a client library ↗ hashicorp/terraform-provider-google-beta
  11. [11] nightly ↗ hashicorp/nomad-driver-podman
  12. [12] nightly ↗ hashicorp/nomad-autoscaler
  13. [13] nightly ↗ hashicorp/nomad-pack

Quick answers

What shipped in HashiCorp on June 13, 2026?
The Terraform Google provider re-landed a critical Apigee feature that was reverted months ago, while simultaneously shipping network and artifact registry enhancements across both stable and beta channels. In total, 16 commits, 16 pull requests, and 3 releases landed.
Who contributed to HashiCorp on June 13, 2026?
1 developer shipped this update, including modular-magician.
What were the notable HashiCorp updates?
apigee: add static consumer_key/consumer_secret to google_apigee_developer_app (re-land with fix), apigee: add static consumer_key/consumer_secret to google_apigee_developer_app (re-land with fix), and artifactregistry: Remove Immutable from upstream_credentials.

More from @hashicorp

Daily updates, in your inbox

Follow HashiCorp

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

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?

We use privacy-friendly analytics (Google Analytics, IP-anonymized) to see which pages help readers. No ads, and we never sell your data. See our Privacy Policy.