RouteTable | Praxis resources

Resource definition

What this resource looks like

This is the CUE shape a Praxis template uses to declare a RouteTable. The resource key is local to the template; metadata.name supplies its stable Praxis identity.

resources: {
  publicRT: {
  	apiVersion: "praxis.io/alpha"
  	kind:       "RouteTable"
  	metadata: name: "\(_naming.prefix)-public-rt"
  	spec: {
  		region: _naming.region
  		vpcId:  "${resources.vpc.outputs.vpcId}"
  		routes: [{
  			destinationCidrBlock: "0.0.0.0/0"
  			gatewayId:            "${resources.igw.outputs.internetGatewayId}"
  		}]
  		associations: [
  			{subnetId: "${resources.publicSubnetA.outputs.subnetId}"},
  			{subnetId: "${resources.publicSubnetB.outputs.subnetId}"},
  		]
  		tags: #WebTags
  	}
  }
}

Excerpted from examples/stacks/end-to-end.cue. Open the complete example for its variables and related resources.

Complete examples in the repository

stacks end to end stacks saas platform stacks three tier app vpc multi az vpc vpc vpc peering

Desired state

Configuration

The spec block accepts 5 fields. 2 are required by the schema; fields with defaults can be omitted.

regionRequired

Region.

string

String

vpcIdRequired

Vpc ID.

string

String

routesOptional

Routes.

[...#Route]

List

associationsOptional

Associations.

[...#Association]

List

tagsOptional

Tags.

[string]: string

Map

Observed values

Outputs

Praxis records these values after observation. A dependent resource can read one with ${resources.<name>.outputs.<field>}.

routeTableIdString

vpcIdString

ownerIdString

routesObject list

associationsObject list

Read without ownership

Data-source lookup

A data block reads an existing RouteTable and exposes its outputs without storing lifecycle state. The generic filter surface accepts id, name, and tag; supported combinations depend on the AWS identity used by this resource.

data: existing: {
  kind: "RouteTable"
  region: "us-west-2"
  filter: {
    name: "replace-with-provider-name"
  }
}

Understand data sources and filters →

Adopt existing infrastructure

Import

Import persists Praxis state for an existing AWS resource. For this kind, supply: Provider identifier for the existing RouteTable. The example starts in observed mode so Praxis reports drift without correcting it.

praxis import RouteTable \
  --id <provider-identifier> \
  --region us-west-2 \
  --account production \
  --observe

Choose managed or observed ownership →

Canonical contract

Complete CUE schema

The field guide above is derived from this definition. The schema remains the source of truth for accepted values, defaults, validation constraints, and outputs in the current alpha revision.

Show the complete schema

package routetable

#RouteTable: {
	apiVersion: "praxis.io/alpha"
	kind:       "RouteTable"

	metadata: {
		name: string & =~"^[a-zA-Z0-9][a-zA-Z0-9._-]{0,254}$"
		labels: [string]: string
	}

	spec: {
		region: string
		vpcId:  string

		routes?: [...#Route]
		associations?: [...#Association]
		tags?: [string]: string
	}

	outputs?: {
		routeTableId: string
		vpcId:        string
		ownerId:      string
		routes: [...{
			destinationCidrBlock:    string
			gatewayId?:              string
			natGatewayId?:           string
			vpcPeeringConnectionId?: string
			transitGatewayId?:       string
			networkInterfaceId?:     string
			vpcEndpointId?:          string
			state:                   string
			origin:                  string
		}]
		associations: [...{
			associationId: string
			subnetId:      string
			main:          bool
		}]
	}
}

#Route: {
	destinationCidrBlock: string & =~"^([0-9]{1,3}\\.){3}[0-9]{1,3}/([0-9]|[12][0-9]|3[0-2])$"

	gatewayId?:              string
	natGatewayId?:           string
	vpcPeeringConnectionId?: string
	transitGatewayId?:       string
	networkInterfaceId?:     string
	vpcEndpointId?:          string
}

#Association: subnetId: string

View this schema on GitHub →