Skip to content

fix: remove GCP-specific arg from AWS orchestrator module#2177

Merged
jakubno merged 1 commit into
e2b-dev:mainfrom
ya-luotao:fix/aws-remove-gcs-pool-size
Mar 19, 2026
Merged

fix: remove GCP-specific arg from AWS orchestrator module#2177
jakubno merged 1 commit into
e2b-dev:mainfrom
ya-luotao:fix/aws-remove-gcs-pool-size

Conversation

@ya-luotao

Copy link
Copy Markdown
Contributor

Summary

  • Removes gcs_grpc_connection_pool_size from the AWS provider's orchestrator module call in iac/provider-aws/nomad/main.tf
  • This argument was introduced in chore(orch): add more info for sandboxes #2174 but is GCP-specific — the orchestrator module only accepts it inside provider_gcp_config, not as a top-level variable
  • Causes terraform plan to fail on the AWS provider with: An argument named "gcs_grpc_connection_pool_size" is not expected here

Test plan

  • Verified terraform plan fails on AWS provider without this fix
  • Run terraform plan on AWS provider after this fix

🤖 Generated with Claude Code

…strator module

The orchestrator module accepts gcs_grpc_connection_pool_size inside
provider_gcp_config, not as a top-level argument. This causes
terraform plan to fail on the AWS provider.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

@jakubno jakubno merged commit a9f40ac into e2b-dev:main Mar 19, 2026
1 check passed
@jakubno

jakubno commented Mar 19, 2026

Copy link
Copy Markdown
Member

Thanks @ya-luotao!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants