/**
 * Agilicus API
 * Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply.  The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools.  A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI.  This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2).  Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com.  If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud.  For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`.  This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go).  100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible.  For more information, see [developer resources](https://www.agilicus.com/developer).
 *
 * The version of the OpenAPI document: 2025.12.16
 * Contact: dev@agilicus.com
 *
 * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
 * https://openapi-generator.tech
 * Do not edit the class manually.
 */
export interface _ConnectorRoute {
    /**
     * Unique identifier
     */
    resource_id: string;
    /**
     * The path uniquely identifying the route to the mentioned resource using the routing given routing_method. This path must be joined with a host and scheme associated to a connector router to actually establish a tunnel.
     */
    routing_path: string;
    /**
     * How to determine the route given the routing_path. The possible values mean:   - `resource_hostname`: route based on the hostname configured for the resource.      example: /named-service/org-1/host/localhost/port/5000   - `resource_id`: route based on the id of the resource.      example: /named-service/org-1/guid/aB8Zm5tuxVia2FQ7i/port/5000 Note that it may indicate a port range, (e.g. /named-service/<org>/host/localhost/port/{{port}}?port:int=5000-5002,5555,5556). In that case when establishing an actual connection, substitute {{port}} with the port you want to connect to, and drop the query string.
     */
    routing_method: string;
}
export interface ConnectorRoute extends _ConnectorRoute {
    _builtin_original?: _ConnectorRoute;
    _remove_builtin_extensions?: () => void;
}
export declare class ConnectorRouteImpl implements _ConnectorRoute {
    _builtin_original?: _ConnectorRoute;
    resource_id: string;
    routing_path: string;
    routing_method: string;
    constructor(base: _ConnectorRoute);
    _remove_builtin_extensions(): void;
}
export declare function newConnectorRouteImpl(base: _ConnectorRoute): ConnectorRouteImpl;