/**
 * WAW065: Transit Gateway Route Table Wiring Is Incomplete
 *
 * A Transit Gateway route table only does anything once two independent
 * pieces are both wired up: an `AWS::EC2::TransitGatewayRouteTableAssociation`
 * (which attachment's traffic is evaluated against this table) and an
 * `AWS::EC2::TransitGatewayRouteTablePropagation` (which attachments' routes
 * populate it). CloudFormation is happy to deploy a route table with one but
 * not the other — the stack succeeds, and the gap only shows up as traffic
 * that can't find a route. Two patterns, both "declared but half-wired":
 *
 *  - a route table has one or more associations but zero propagations — the
 *    associated attachment's traffic is evaluated against this table, but
 *    nothing ever populates it with routes;
 *  - a declared attachment (VPC/VPN/peering, or the generic
 *    TransitGatewayAttachment) is referenced by neither an association nor
 *    a propagation anywhere in the template — it hangs off the transit
 *    gateway with no route table wiring at all.
 */
import type { PostSynthCheck, PostSynthContext, PostSynthDiagnostic } from "@intentius/chant/lint/post-synth";
export declare function checkTgwRouteTableWiring(ctx: PostSynthContext): PostSynthDiagnostic[];
export declare const waw065: PostSynthCheck;
//# sourceMappingURL=waw065.d.ts.map