Skip to content

Fix GCP assignment failure for STANDARD tier IP addresses#170

Open
javibookline wants to merge 1 commit intodoitintl:masterfrom
javibookline:fix/standard-network-tier-ipv4
Open

Fix GCP assignment failure for STANDARD tier IP addresses#170
javibookline wants to merge 1 commit intodoitintl:masterfrom
javibookline:fix/standard-network-tier-ipv4

Conversation

@javibookline
Copy link

Summary

  • Set NetworkTier on IPv4 access configs when the address uses a non-default tier (e.g. STANDARD), matching the existing IPv6 behavior
  • Previously, NetworkTier was only set for IPv6 addresses in createAccessConfig(), causing IPv4 STANDARD tier addresses to fail with: External IP address has a different network tier STANDARD from the network tier in instance access config PREMIUM
  • The fix is fully backward compatible: PREMIUM tier addresses (the default) are unaffected, and only non-default tiers like STANDARD are explicitly set

Closes #155

Test plan

  • All existing tests pass unmodified
  • New test case added for STANDARD tier IPv4 address
  • Full test suite passes (go test ./...)

Set NetworkTier on IPv4 access configs using the addressNetworkTierOrDefault
helper, matching the existing IPv6 behavior. Previously, NetworkTier was
only set for IPv6 addresses, causing IPv4 STANDARD tier addresses to fail
with a network tier mismatch error.

Closes doitintl#155

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@javibookline javibookline force-pushed the fix/standard-network-tier-ipv4 branch from 7857856 to cc81395 Compare February 16, 2026 15:16
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.

GCP assignment fails if IP address is of STANDARD tier

1 participant