Route Table

Network route tables contain a set of rules, called routes, that are used to determine where network traffic is directed. Each subnet in your VPC must be associated with a route table; the table controls the routing for the subnet. A subnet can only be associated with one route table at a time, but you can associate multiple subnets with the same route table. This class inherits from Resource and has direct access to the resource’s database object

Attribute

Description

resource_id

The provider ID of this route table

organization_service_id

The ID of the organization service (cloud) this access list belongs to

region_name

The region where this resource resides in

name

The name of this route table

network_resource_id

The resource ID of the parent (network)

vpc_association_id

The the virtual private cloud that this route table is associated with

routes

The routes that belong to this table

Route Table Operations

delete(user_resource_id=None)
Delete this resource. If wrapped in a with JobQueue() block, this will queue the deletion job to the wrapped queue, otherwise it calls immediately.

static get_db_class()

get_network_id()
Retrieve the network ID that the route table belongs to.

static get_provider_id_field()

static get_resource_type()

get_supported_actions()

get_vpc_association_id()
Retrieve the VPC association ID of the route.
handle_resource_created(user_resource_id=None, project_resource_id=None)
This should be called when a resource is created/discovered after the basic data is added to the database. This gives an opportunity for post-addition hooks (assignment to groups, alerts, etc).
handle_resource_destroyed(user_resource_id=None)
This should be called when a resource is destroyed before the basic data is removed from the database. This gives an opportunity for pre-destruction hooks (removal from groups, alerts, etc).
handle_resource_modified(resource, *args, **kwargs)
This should be called when a resource is modified after the new data has been updated in the DB session. This gives an opportunity for post-modification hooks.

route_table

route_table_id