$ the-wire · showcase
AWS provider grows prefix allocations, Vertex AI drift fix lands
By RepoJournal · Filed · About HashiCorp
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4)
7 people shipped this
modular-magician
@modular-magician
2 cited
StephenKing
@StephenKing
1 cited
jesseturner21
@jesseturner21
1 cited
madhavvishnubhatta
@madhavvishnubhatta
1 cited
ewbankkit
@ewbankkit
1 cited
github-actions[bot]
@github-actions[bot]
1 cited
hc-github-team-nomad-ecosystem
@hc-github-team-nomad-ecosystem
1 cited
Terraform's AWS provider adds Direct Connect prefix allocation support, Google Beta fixes a Vertex AI read no-op, and both Nomad projects roll nightly snapshots.
The AWS provider [1] implements new parameters for inbound route-prefix allocations on private and transit virtual interfaces, giving Direct Connect users explicit control over advertised prefixes. Separately, the provider adds HTTP passthrough targets to `aws_bedrockagentcore_gateway_target` [2], completing the previously-unimplemented second member of the HTTP target union with its schema and stickiness configuration. For EKS, the provider mirrors the resource's `pod_gc_controller_config` block into the `aws_eks_cluster` data source [3], exposing `terminated_pod_gc_threshold` for data-driven configs. The Google Beta provider fixes a real drift blind spot: `google_vertex_ai_endpoint_with_model_garden_deployment` generated a no-op Read [4], so out-of-band changes were invisible and `terraform plan` reported "No changes" on drifted state; it now reads back replica counts, the only mutable field. Google Beta also adds `proactive_execution_enabled` to `code_callback` callbacks [5], enabling guardrail callbacks to run proactively. Both `nomad-driver-podman` [6] and `nomad-pack` [7] publish nightly snapshots for testing upcoming fixes, and the AWS provider ships a new list resource `aws_lambdamicrovms_image` [8].
Action items
- → Review Direct Connect prefix allocation parameters before next AWS provider config change hashicorp/terraform-provider-aws [plan]
- → Apply the Google Beta provider update to get drift detection on Vertex AI model garden endpoints hashicorp/terraform-provider-google-beta [plan]
- → Test Nomad workflows against the nomad-pack nightly snapshot for upcoming fixes hashicorp/nomad-pack [monitor]
References
- [1] Prefix allocations for Direct Connect virtual interfaces ↗ hashicorp/terraform-provider-aws
- [2] r/aws_bedrockagentcore_gateway_target: add HTTP passthrough target with schema and stickiness ↗ hashicorp/terraform-provider-aws
- [3] F data source eks kube controller manager config ↗ hashicorp/terraform-provider-aws
- [4] fix(vertexai): implement Read for EndpointWithModelGardenDeployment ↗ hashicorp/terraform-provider-google-beta
- [5] ces: add proactive_execution_enabled to ces_guardrail code_callback ↗ hashicorp/terraform-provider-google-beta
- [6] nightly ↗ hashicorp/nomad-driver-podman
- [7] nightly ↗ hashicorp/nomad-pack
- [8] New list resource: `aws_lambdamicrovms_image` ↗ hashicorp/terraform-provider-aws
