/**
 * 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.
 */
import { PointOfPresenceRouting } from './pointOfPresenceRouting';
export interface _PointOfPresenceSpec {
    /**
     * The name of a tag. Tag names are case sensitive.
     */
    name: string;
    /**
     * Properties of the point of presence such as different aspects of its geographical location. These can be used to filter point of presences based on desired properties.
     */
    tags: Array<string>;
    routing: PointOfPresenceRouting;
    /**
     * Designates a particular cluster in the PointOfPresence as a master.  This property is normally not required when there is a single cluster_id specified in cluster_ids.  This guid must also exist inside cluster_ids.
     */
    master_cluster_id?: string;
    /**
     * the configured cluster ids that are associated to this PointOfPresence
     */
    cluster_ids?: Array<string>;
    /**
     * Organisation subdomains supported by this PointOfPresence
     */
    org_domains?: Array<string>;
}
export interface PointOfPresenceSpec extends _PointOfPresenceSpec {
    _builtin_original?: _PointOfPresenceSpec;
    _remove_builtin_extensions?: () => void;
}
export declare class PointOfPresenceSpecImpl implements _PointOfPresenceSpec {
    _builtin_original?: _PointOfPresenceSpec;
    name: string;
    tags: Array<string>;
    routing: PointOfPresenceRouting;
    master_cluster_id: string | undefined;
    cluster_ids: Array<string> | undefined;
    org_domains: Array<string> | undefined;
    constructor(base: _PointOfPresenceSpec);
    _remove_builtin_extensions(): void;
}
export declare function newPointOfPresenceSpecImpl(base: _PointOfPresenceSpec): PointOfPresenceSpecImpl;