scaleway/private-network v0.1.0
Three new single-resource modules for the Scaleway networking that compute-cluster creates inline today. They back the scaleway.privateNetwork and scaleway.publicGateway workload kinds and the PAT rule a workload instance's network.sshViaGateway implies (LIB-0043 §7). Each starts at v0.1.0.
scaleway/private-networkwraps onescaleway_vpc_private_network. It takesnameandproject_id, and outputsidandname.scaleway/public-gatewaycreates a gateway's public IP, the gateway, and its attachment to one Private Network. It takesname,project_id,private_network_idandtype(VPC-GW-Sby default, validated against the four offers, upgrade-only).enable_masqueradeandpush_default_routeboth default totrue, ascompute-clustersets them. It outputsid,ip_addressandgateway_network_id. The three resources sit in one module because they're always one to one and no other module wraps any of them.scaleway/gateway-pat-rulewraps onescaleway_vpc_public_gateway_pat_rule, forwardingpublic_porton a gateway's IP toprivate_ip:private_port(port 22 andtcpby default). It outputsidand, for a rule to port 22, aconnect_command.
While a gateway pushes its default route, an attached instance's own public IP works outbound only (ADR-0146), so a PAT rule is the way in.
Verified with tofu init and tofu validate on each module, and tofu fmt -check. No plan was run against a live project.
🤖 Generated with Claude Code
PR: https://github.com/noisypigeon/library/pull/220