Skip to main content

stack_needs_named_subnets_at_setup

Function stack_needs_named_subnets_at_setup 

Source
pub fn stack_needs_named_subnets_at_setup(stack: &Stack) -> bool
Expand description

Whether any setup-owned resource forces setup to name subnets.

Private databases and restricted sandbox connectors require subnet IDs. Neither generator can enumerate the account default VPC’s subnets. Callers rendering an artifact want restricts_network_mode instead: this one answers for the declaration, which on a Kubernetes target is not what gets emitted.