import { Service } from '../Core/index';
import { MacroCompletion, MacroDebugBreakpointSet, MacroDebugInfoRequest, MacroDebugSession, MacroDebugStep, MacroDebugVariableChange, MacroExecBaseUrl, MacroFunctionRequest, MacroFunctionResult, MacroPlay, SuMacroPlay } from './MacroTypes';
/**
 * Macros
 *
 * Macro-command service
 *  An admin defines macro-commands that can sequentially call any number of other api verbs, loop on collections of data, make decisions, etc
 *
 *
 *  End-users play them, with contextual parameters
 * */
export declare class Macro extends Service {
    /**
     * Get deployment type associated to Macro service
     * @return {string}
     */
    static readonly DEPLOYMENT_TYPE: string;
    /**
     * Get default deployment id associated to Macro service
     * @return {string}
     */
    static readonly DEFAULT_DEPLOYMENT_ID: string;
    /**
     * User API for macro debugging
     *
     * Debugger API for macro.
     * These API verbs are not intended for use by most developers.
     * @access public
     * */
    /**
     * Enables or disables a breakpoint
     *
     * @access public
     * */
    breakpoint(body: MacroDebugBreakpointSet): void;
    /**
     * Requests some information
     *
     * @access public
     * */
    info(body: MacroDebugInfoRequest): void;
    /**
     * Debugs a previously recorded macro
     *
     * The given breakpoints will be honored, causing a suspension of the execution, resumable via 'resume'.
     * Only one debug session can be active at any given time.
     * @access public
     * */
    livedebug(body: MacroDebugSession): void;
    /**
     * Resumes a paused macro
     *
     * @access public
     * */
    resume(body: MacroDebugStep): void;
    /**
     * Sets a variable value
     *
     * @access public
     * */
    variable(body: MacroDebugVariableChange): void;
    /**
     * User API for macro execution
     *
     * Simple errors are reported as usual.
     * However, the macro execution verbs treat most errors in a particular way : instead of reporting errors on the usual 'error' channel, errors are put in the returned 'MacroCompletion' result.
     * This behavior can be tuned on a per-call basis with the hardFail parameter.
     * Note that some particular errors will always behave as if hardFail were true, because they are related to programming errors, or prevent processing from ending gracefully : STACK_OVERFLOW, NO_SUCH_FUNCTION, RAM_EXCEEDED, CYCLES_EXCEEDED, TIME_EXCEEDED, QUOTA_EXCEEDED, RATE_EXCEEDED, BAD_COMPARATOR_VALUE
     * @access public
     * */
    /**
     * Plays a previously recorded macro
     *
     * DO NOT use this verb from inside an enclosing macro when you need the result in order to proceed with the enclosing macro.
     * You can override the default notification channel when defining the macro.
     * @access public
     * */
    call(body: MacroPlay): void;
    /**
     * Evaluates a function result.
     *
     * @access public
     * */
    evaluate(body: MacroFunctionRequest): Promise<MacroFunctionResult>;
    /**
     * Plays a previously recorded macro and returns the result.
     *
     * Use this verb when you want to synchronously call a macro from inside another macro.
     * Despite being a server verb, func will honor the 'loud' modifier in ZMS.
     * @access public
     * */
    func(body: MacroPlay): Promise<MacroCompletion>;
    /**
     * Returns the base HTTP URL for 'macro/exec' in this macro service.
     *
     * @access public
     * */
    getPublicHttpUrl(): Promise<MacroExecBaseUrl>;
    /**
     * Similar to func, with the ability to impersonate any user at will.
     *
     * Use this verb when you do not want to use or cannot use the standard rights system and wish to bypass it completely.
     * Use this verb sparingly, as it can give the caller any right on any resource.
     * @access public
     * */
    sudo(body: SuMacroPlay): Promise<MacroCompletion>;
}