/**
  Juju Bundle version 6.
  This facade is available on:
    Controllers
    Models

  NOTE: This file was generated using the Juju schema
  from Juju 3.3 at the git SHA 65fa4c1ee5.
  Do not manually edit this file.
*/
import { ConnectionInfo, Transport } from "../../client.js";
import { Facade } from "../../types.js";
export interface BundleChange {
    args: object[];
    id: string;
    method: string;
    requires: string[];
}
export interface BundleChangesMapArgs {
    args: AdditionalProperties;
    id: string;
    method: string;
    requires: string[];
}
export interface BundleChangesMapArgsResults {
    changes?: BundleChangesMapArgs[];
    errors?: string[];
}
export interface BundleChangesParams {
    bundleURL: string;
    yaml: string;
}
export interface BundleChangesResults {
    changes?: BundleChange[];
    errors?: string[];
}
export interface Error {
    code: string;
    info?: AdditionalProperties;
    message: string;
}
export interface ExportBundleParams {
    "include-charm-defaults"?: boolean;
    "include-series"?: boolean;
}
export interface StringResult {
    error?: Error;
    result: string;
}
export interface AdditionalProperties {
    [key: string]: any;
}
/**
  APIv6 provides the Bundle API facade for version 6. It is otherwise
  identical to V5 with the exception that the V6 adds the support for
  multi-part yaml handling to GetChanges and GetChangesMapArgs.
*/
declare class BundleV6 implements Facade {
    static NAME: string;
    static VERSION: number;
    NAME: string;
    VERSION: number;
    _transport: Transport;
    _info: ConnectionInfo;
    constructor(transport: Transport, info: ConnectionInfo);
    /**
      ExportBundle exports the current model configuration as bundle.
    */
    exportBundle(params: ExportBundleParams): Promise<StringResult>;
    /**
      GetChanges returns the list of changes required to deploy the given bundle
      data. The changes are sorted by requirements, so that they can be applied in
      order.
      GetChanges has been superseded in favour of GetChangesMapArgs. It's
      preferable to use that new method to add new functionality and move clients
      away from this one.
    */
    getChanges(params: BundleChangesParams): Promise<BundleChangesResults>;
    /**
      GetChangesMapArgs returns the list of changes required to deploy the given
      bundle data. The changes are sorted by requirements, so that they can be
      applied in order.
      V4 GetChangesMapArgs is not supported on anything less than v4
    */
    getChangesMapArgs(params: BundleChangesParams): Promise<BundleChangesMapArgsResults>;
}
export default BundleV6;