/**
 * 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 { FileTemplateParameter } from './fileTemplateParameter';
import { FileTemplateAssociation } from './fileTemplateAssociation';
import { FileTemplateArgument } from './fileTemplateArgument';
export interface _FileTemplateSpec {
    /**
     * The list of parameters this template will accept. Note that by default the `user.X` and `resource.X` parameters are always accepted.
     */
    template_parameters: Array<FileTemplateParameter>;
    /**
     * The content type to return on read. The template engine will automatically determine whether the content needs to be extracted.
     */
    template_content_type: string;
    /**
     * A list of arguments to provide by default when rendering the template. These may be overridden by the render request.
     */
    default_arguments: Array<FileTemplateArgument>;
    /**
     * the purpose of the template. helps with deciding whether it should be used for a given operation.
     */
    purpose: string;
    /**
     * Unique identifier
     */
    template_file?: string;
    /**
     * Unique identifier
     */
    org_id: string;
    /**
     * Optionally used by a client to describe the template files to users. For example, the client may provide an action button saying: \"Download Project File\"
     */
    descriptive_text: string;
    /**
     * Objects associated with this file template. Useful for finding relevant templates.
     */
    associated_objects?: Array<FileTemplateAssociation>;
    /**
     * What to call the rendered file when downloading.
     */
    rendered_file_name: string;
    /**
     * The delimiter used to identify placeholders. For example, if the delimiter is $, the possible placeholders for parameter `foo` are: ```   $foo   ${foo} ``` If the delimiter is %$ then the placeholders for `foo` are: ``` %$foo %${foo} ```
     */
    delimiter?: string;
}
export interface FileTemplateSpec extends _FileTemplateSpec {
    _builtin_original?: _FileTemplateSpec;
    _remove_builtin_extensions?: () => void;
}
export declare class FileTemplateSpecImpl implements _FileTemplateSpec {
    _builtin_original?: _FileTemplateSpec;
    template_parameters: Array<FileTemplateParameter>;
    template_content_type: string;
    default_arguments: Array<FileTemplateArgument>;
    purpose: string;
    template_file: string | undefined;
    org_id: string;
    descriptive_text: string;
    associated_objects: Array<FileTemplateAssociation> | undefined;
    rendered_file_name: string;
    delimiter: string | undefined;
    constructor(base: _FileTemplateSpec);
    _remove_builtin_extensions(): void;
}
export declare function newFileTemplateSpecImpl(base: _FileTemplateSpec): FileTemplateSpecImpl;