@dynatrace-sdk/client-classic-environment-v2 0.6.1

package/types/packages/client/classic-environment-v2/src/lib/apis/settings-objects-api.d.ts

@@ -0,0 +1,175 @@
+import { AbortSignal, HttpClient } from '@dynatrace-sdk/http-client';
+import { EffectiveSettingsValuesList } from '../models/effective-settings-values-list';
+import { ObjectsList } from '../models/objects-list';
+import { SettingsObject } from '../models/settings-object';
+import { SettingsObjectCreate } from '../models/settings-object-create';
+import { SettingsObjectResponse } from '../models/settings-object-response';
+import { SettingsObjectUpdate } from '../models/settings-object-update';
+/**
+ * Manage settings objects
+ */
+export declare class SettingsObjectsClient {
+    private httpClient;
+    /**
+     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a SettingsObjectsClient. Custom http client should implement {HttpClient} interface.
+     * @example
+     * const queryClientNodeJs = new QueryClient(yourCustomImplementation);
+     */
+    constructor(httpClientImplementation: HttpClient);
+    /**
+     * Gets the specified settings object
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + settings:objects:read
+     * @returns Success
+     */
+    getSettingsObjectByObjectId(config: {
+        /** The ID of the required settings object. */ objectId: string;
+        abortSignal?: AbortSignal;
+    }): Promise<SettingsObject>;
+    /**
+     * Updates an existing settings object
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + settings:objects:write
+     * @returns Success
+     */
+    putSettingsObjectByObjectId(config: {
+        body: SettingsObjectUpdate;
+        /** The ID of the required settings object. */ objectId: string;
+        abortSignal?: AbortSignal;
+    }): Promise<SettingsObjectResponse>;
+    /**
+     * Deletes the specified settings object
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + settings:objects:write
+     */
+    deleteSettingsObjectByObjectId(config: {
+        /** The ID of the required settings object. */ objectId: string;
+        /**
+         * The update token of the object. You can use it to detect simultaneous modifications by different users.
+         *
+         * It is generated upon retrieval (GET requests). If set on update (PUT request) or deletion, the update/deletion will be allowed only if there wasn't any change between the retrieval and the update.
+         *
+         * If omitted on update/deletion, the operation overrides the current value or deletes it without any checks.
+         */ updateToken?: string;
+        abortSignal?: AbortSignal;
+    }): Promise<void>;
+    /**
+     * Lists effective settings values
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + settings:objects:read
+     * <br/><br/>Lists effective settings values for selected schemas at a selected scope (or entity). This operation evaluates the hierarchy of persisted objects (see [/settings/objects](#/Settings%20-%20Objects/getSettingsObjects))
+     *
+     * It will always return a result for a schema/scope combination, even if the schema would not be relevant to the given scope/entity.
+     *
+     * If no object along the hierarchy is persisted, the default value as defined in the schema will be returned.
+     * @returns Success
+     */
+    getEffectiveSettingsValues(config: {
+        /**
+         * A list of comma-separated schema IDs to which the requested objects belong.
+         *
+         * Only considered on load of the first page, when the **nextPageKey** is not set.
+         */ schemaIds?: string;
+        /**
+         * The scope that the requested objects target.
+         *
+         * The selection only matches objects directly targeting the specified scope. For example, `environment` will not match objects that target a host within environment.
+         *
+         * To load the first page, when the **nextPageKey** is not set, this parameter is required.
+         */ scope?: string;
+        /**
+         * A list of fields to be included to the response. The provided set of fields replaces the default set.
+         *
+         *  Specify the required top-level fields, separated by commas (for example, `origin,value`).
+         */ fields?: string;
+        /**
+         * The cursor for the next page of results. You can find it in the **nextPageKey** field of the previous response.
+         *
+         * The first page is always returned if you don't specify the **nextPageKey** query parameter.
+         *
+         * When the **nextPageKey** is set to obtain subsequent pages, you must omit all other query parameters.
+         */ nextPageKey?: string;
+        /**
+         * The amount of settings objects in a single response payload.
+         *
+         * The maximal allowed page size is 500.
+         *
+         * If not set, 100 is used.
+         */ pageSize?: number;
+        abortSignal?: AbortSignal;
+    }): Promise<EffectiveSettingsValuesList>;
+    /**
+     * Lists persisted settings objects
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + settings:objects:read
+     * <br/><br/>Lists persisted settings objects for selected schemas at selected scopes (or entities).
+     *
+     * If nothing is persisted or if all persisted settings objects are not accessible due to missing permissions, no items will be returned.
+     *
+     * To query the effective values (including schema defaults) please see [/settings/effectiveValues](#/Settings%20-%20Objects/getEffectiveSettingsValues).
+     * @returns Success. Accessible objects returned.
+     */
+    getSettingsObjects(config: {
+        /**
+         * A list of comma-separated schema IDs to which the requested objects belong.
+         *
+         * To load the first page, when the **nextPageKey** is not set, either this parameter or **scopes** is required.
+         *
+         * To load all objects belonging to the given schema IDs leave the **scopes** parameter empty.
+         */ schemaIds?: string;
+        /**
+         * A list of comma-separated scopes, that the requested objects target.
+         *
+         * The selection only matches objects directly targeting the specified scopes. For example, `environment` will not match objects that target a host within environment.
+         *
+         * To load the first page, when the **nextPageKey** is not set, either this parameter or **schemaIds** is required.
+         *
+         * To load all objects belonging to the given scopes leave the **schemaIds** parameter empty.
+         */ scopes?: string;
+        /**
+         * A list of fields to be included to the response. The provided set of fields replaces the default set.
+         *
+         *  Specify the required top-level fields, separated by commas (for example, `objectId,value`).
+         */ fields?: string;
+        /**
+         * The cursor for the next page of results. You can find it in the **nextPageKey** field of the previous response.
+         *
+         * The first page is always returned if you don't specify the **nextPageKey** query parameter.
+         *
+         * When the **nextPageKey** is set to obtain subsequent pages, you must omit all other query parameters.
+         */ nextPageKey?: string;
+        /**
+         * The amount of settings objects in a single response payload.
+         *
+         * The maximal allowed page size is 500.
+         *
+         * If not set, 100 is used.
+         */ pageSize?: number;
+        abortSignal?: AbortSignal;
+    }): Promise<ObjectsList>;
+    /**
+     * Creates a new settings object
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + settings:objects:write
+     * <br/><br/>You can upload several objects at once. In that case each object returns its own response code. Check the response body for details.
+     * @returns Success
+     */
+    postSettingsObjects(config: {
+        body: SettingsObjectCreate[];
+        /** If `true`, the request runs only validation of the submitted settings objects, without saving them. */ validateOnly?: boolean;
+        abortSignal?: AbortSignal;
+    }): Promise<SettingsObjectResponse[]>;
+}
+export declare const settingsObjectsClient: SettingsObjectsClient;

package/types/packages/client/classic-environment-v2/src/lib/apis/settings-schemas-api.d.ts

@@ -0,0 +1,42 @@
+import { AbortSignal, HttpClient } from '@dynatrace-sdk/http-client';
+import { SchemaDefinitionRestDto } from '../models/schema-definition-rest-dto';
+import { SchemaList } from '../models/schema-list';
+/**
+ * View settings schemas
+ */
+export declare class SettingsSchemasClient {
+    private httpClient;
+    /**
+     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a SettingsSchemasClient. Custom http client should implement {HttpClient} interface.
+     * @example
+     * const queryClientNodeJs = new QueryClient(yourCustomImplementation);
+     */
+    constructor(httpClientImplementation: HttpClient);
+    /**
+     * Lists available settings schemas
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + settings:schemas:read
+     * @returns Success
+     */
+    getAvailableSchemaDefinitions(abortSignal?: AbortSignal): Promise<SchemaList>;
+    /**
+     * Gets parameters of the specified settings schema
+     *
+     * **One of the following scopes is required:**
+     * + environment-api
+     * + settings:schemas:read
+     * @returns Success
+     */
+    getSchemaDefinition(config: {
+        /** The ID of the required schema. */ schemaId: string;
+        /**
+         * The version of the required schema.
+         *
+         *  If not set, the most recent version is returned.
+         */ schemaVersion?: string;
+        abortSignal?: AbortSignal;
+    }): Promise<SchemaDefinitionRestDto>;
+}
+export declare const settingsSchemasClient: SettingsSchemasClient;

package/types/packages/client/classic-environment-v2/src/lib/apis/synthetic-http-monitor-executions-api.d.ts

@@ -0,0 +1,25 @@
+import { AbortSignal, HttpClient } from '@dynatrace-sdk/http-client';
+import { GetExecutionResultPathResultType } from '../models/get-execution-result-path-result-type';
+import { MonitorExecutionResults } from '../models/monitor-execution-results';
+export declare class SyntheticHttpMonitorExecutionsClient {
+    private httpClient;
+    /**
+     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a SyntheticHttpMonitorExecutionsClient. Custom http client should implement {HttpClient} interface.
+     * @example
+     * const queryClientNodeJs = new QueryClient(yourCustomImplementation);
+     */
+    constructor(httpClientImplementation: HttpClient);
+    /**
+     * Gets detailed information about the last execution of the specified HTTP monitor | maturity=EARLY_ADOPTER
+     *
+     * **Required scope:** environment-api:synthetic-execution:read
+     * @returns Success. The response contains detailed data.
+     */
+    getExecutionResult(config: {
+        /** Identifier of the HTTP monitor for which last execution result is returned. */ monitorId: string;
+        /** Defines the result type of the last HTTP monitor's execution. */ resultType: GetExecutionResultPathResultType;
+        /** Filters the results to those executed by specified Synthetic location. Specify the ID of the location. */ locationId?: string;
+        abortSignal?: AbortSignal;
+    }): Promise<MonitorExecutionResults>;
+}
+export declare const syntheticHttpMonitorExecutionsClient: SyntheticHttpMonitorExecutionsClient;

package/types/packages/client/classic-environment-v2/src/lib/apis/synthetic-locations-nodes-and-configuration-api.d.ts

@@ -0,0 +1,46 @@
+import { AbortSignal, HttpClient } from '@dynatrace-sdk/http-client';
+import { SyntheticConfigDto } from '../models/synthetic-config-dto';
+import { SyntheticPublicLocationsStatus } from '../models/synthetic-public-locations-status';
+export declare class SyntheticLocationsNodesAndConfigurationClient {
+    private httpClient;
+    /**
+     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a SyntheticLocationsNodesAndConfigurationClient. Custom http client should implement {HttpClient} interface.
+     * @example
+     * const queryClientNodeJs = new QueryClient(yourCustomImplementation);
+     */
+    constructor(httpClientImplementation: HttpClient);
+    /**
+     * Gets set of synthetic related parameters defined for whole tenant (affects all monitors and all private locations). | maturity=EARLY_ADOPTER
+     *
+     * **Required scope:** environment-api:synthetic:read
+     * @returns Success. The response contains synthetic related parameters defined for whole tenant.
+     */
+    getConfiguration(abortSignal?: AbortSignal): Promise<SyntheticConfigDto>;
+    /**
+     * Updates set of synthetic related parameters defined for whole tenant (affects all monitors and all private locations). | maturity=EARLY_ADOPTER
+     *
+     * **Required scope:** environment-api:synthetic:write
+     * @returns Success. The set of synthetic related parameters has been updated. Response doesn't have a body.
+     */
+    updateConfiguration(config: {
+        body: SyntheticConfigDto;
+        abortSignal?: AbortSignal;
+    }): Promise<SyntheticConfigDto>;
+    /**
+     * Checks the status of public synthetic locations
+     *
+     * **Required scope:** environment-api:synthetic:read
+     * @returns Success. The response contains the public locations status.
+     */
+    getLocationsStatus(abortSignal?: AbortSignal): Promise<SyntheticPublicLocationsStatus>;
+    /**
+     * Changes the status of public synthetic locations
+     *
+     * **Required scope:** environment-api:synthetic:write
+     */
+    updateLocationsStatus(config: {
+        body: SyntheticPublicLocationsStatus;
+        abortSignal?: AbortSignal;
+    }): Promise<void>;
+}
+export declare const syntheticLocationsNodesAndConfigurationClient: SyntheticLocationsNodesAndConfigurationClient;

package/types/packages/client/classic-environment-v2/src/lib/apis/synthetic-on-demand-monitor-executions-api.d.ts

@@ -0,0 +1,184 @@
+import { AbortSignal, HttpClient } from '@dynatrace-sdk/http-client';
+import { GetExecutionsQueryExecutionStage } from '../models/get-executions-query-execution-stage';
+import { GetExecutionsQuerySource } from '../models/get-executions-query-source';
+import { SyntheticOnDemandBatchStatus } from '../models/synthetic-on-demand-batch-status';
+import { SyntheticOnDemandExecution } from '../models/synthetic-on-demand-execution';
+import { SyntheticOnDemandExecutionRequest } from '../models/synthetic-on-demand-execution-request';
+import { SyntheticOnDemandExecutionResult } from '../models/synthetic-on-demand-execution-result';
+import { SyntheticOnDemandExecutions } from '../models/synthetic-on-demand-executions';
+/**
+ * Trigger and view information about on-demand synthetic monitor executions
+ */
+export declare class SyntheticOnDemandMonitorExecutionsClient {
+    private httpClient;
+    /**
+     * @param {HttpClient} httpClientImplementation - You can provide custom http client as a parameter to constructor of a SyntheticOnDemandMonitorExecutionsClient. Custom http client should implement {HttpClient} interface.
+     * @example
+     * const queryClientNodeJs = new QueryClient(yourCustomImplementation);
+     */
+    constructor(httpClientImplementation: HttpClient);
+    /**
+     * Triggers on-demand executions for synthetic monitors | maturity=EARLY_ADOPTER
+     *
+     * **Required scope:** environment-api:synthetic-execution:write
+     * @returns Success. The monitor's execution response details
+     */
+    execute(config: {
+        body: SyntheticOnDemandExecutionRequest;
+        abortSignal?: AbortSignal;
+    }): Promise<SyntheticOnDemandExecutionResult>;
+    /**
+     * Gets summary information and the list of failed executions for the given batch ID | maturity=EARLY_ADOPTER
+     *
+     * **Required scope:** environment-api:synthetic-execution:read
+     * @returns Success
+     */
+    getBatch(config: {
+        /** The batch identifier of the executions. */ batchId: number;
+        abortSignal?: AbortSignal;
+    }): Promise<SyntheticOnDemandBatchStatus>;
+    /**
+     * Gets basic results of the specified on-demand execution | maturity=EARLY_ADOPTER
+     *
+     * **Required scope:** environment-api:synthetic-execution:read
+     * @returns Success. The response contains basic information about the on-demand execution.
+     */
+    getExecution(config: {
+        /** The identifier of the on-demand execution. */ executionId: number;
+        abortSignal?: AbortSignal;
+    }): Promise<SyntheticOnDemandExecution>;
+    /**
+     * Gets detailed results of the specified on-demand execution | maturity=EARLY_ADOPTER
+     *
+     * **Required scope:** environment-api:synthetic-execution:read
+     * @returns Success. The response contains detailed information about the on-demand execution.
+     */
+    getExecutionFullReport(config: {
+        /** The identifier of the on-demand execution. */ executionId: number;
+        abortSignal?: AbortSignal;
+    }): Promise<SyntheticOnDemandExecution>;
+    /**
+     * Gets the list of all on-demand executions of synthetic monitors | maturity=EARLY_ADOPTER
+     *
+     * **Required scope:** environment-api:synthetic-execution:read
+     * @returns Success
+     */
+    getExecutions(config: {
+        /** Filters the resulting set of executions by their stage. */ executionStage?: GetExecutionsQueryExecutionStage;
+        /**
+         * The start of the requested timeframe for scheduling timestamps.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the maximum relative timeframe of six hours is used (`now-6h`).
+         */ schedulingFrom?: string;
+        /**
+         * The end of the requested timeframe for scheduling timestamps.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the current timestamp is used.
+         */ schedulingTo?: string;
+        /**
+         * The start of the requested timeframe for execution timestamps.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the maximum relative timeframe of six hours is used (`now-6h`).
+         */ executionFrom?: string;
+        /**
+         * The end of the requested timeframe for execution timestamps.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the current timestamp is used.
+         */ executionTo?: string;
+        /**
+         * The start of the requested timeframe for data delivering timestamps.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the maximum relative timeframe of six hours is used (`now-6h`).
+         */ dataDeliveryFrom?: string;
+        /**
+         * The end of the requested timeframe for data delivering timestamps.
+         *
+         * You can use one of the following formats:
+         * * Timestamp in UTC milliseconds.
+         * * Human-readable format of `2021-01-25T05:57:01.123+01:00`. If no time zone is specified, UTC is used. You can use a space character instead of the `T`. Seconds and fractions of a second are optional.
+         * * Relative timeframe, back from now. The format is `now-NU/A`, where `N` is the amount of time, `U` is the unit of time, and `A` is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, `now-1y/w` is one year back, aligned by a week.
+         * You can also specify relative timeframe without an alignment: `now-NU`.
+         * Supported time units for the relative timeframe are:
+         *    * `m`: minutes
+         *    * `h`: hours
+         *    * `d`: days
+         *    * `w`: weeks
+         *    * `M`: months
+         *    * `y`: years
+         *
+         * If not set, the current timestamp is used.
+         */ dataDeliveryTo?: string;
+        /** Filters the resulting set of the executions by batch. Specify the ID of the batch. */ batchId?: number;
+        /** Filters the resulting set of the executions by monitor synthetic monitor. Specify the ID of the monitor. */ monitorId?: string;
+        /** Filters the resulting set of the executions by Synthetic location. Specify the ID of the location. */ locationId?: string;
+        /** Filters the resulting set of executions by scheduled user. */ userId?: string;
+        /** Filters the resulting set of the executions by the source of the triggering request. */ source?: GetExecutionsQuerySource;
+        abortSignal?: AbortSignal;
+    }): Promise<SyntheticOnDemandExecutions>;
+}
+export declare const syntheticOnDemandMonitorExecutionsClient: SyntheticOnDemandMonitorExecutionsClient;

package/types/packages/client/classic-environment-v2/src/lib/error-envelopes/api-client-error.d.ts

@@ -0,0 +1,7 @@
+/**
+ * Error base. All client errors should extend this class.
+ */
+export declare class ApiClientError extends Error {
+    constructor(name: string, message?: string);
+}
+export declare function isApiClientError(e: any): e is ApiClientError;

package/types/packages/client/classic-environment-v2/src/lib/error-envelopes/client-request-error.d.ts

@@ -0,0 +1,8 @@
+import { HttpClientResponse } from '@dynatrace-sdk/http-client';
+import { ApiClientError } from './api-client-error';
+export declare class ClientRequestError<DTO> extends ApiClientError {
+    body: DTO;
+    response: HttpClientResponse;
+    constructor(name: string, response: HttpClientResponse, body: DTO, message?: string);
+}
+export declare function isClientRequestError<DTO>(e: any): e is ClientRequestError<DTO>;

package/types/packages/client/classic-environment-v2/src/lib/error-envelopes/error-envelope-error.d.ts

@@ -0,0 +1,8 @@
+/**
+ * ErrorEnvelope
+ */
+import { ClientRequestError } from './client-request-error';
+import { ErrorEnvelope } from '../models';
+export declare class ErrorEnvelopeError extends ClientRequestError<ErrorEnvelope> {
+}
+export declare function isErrorEnvelopeError(e: any): e is ErrorEnvelopeError;

package/types/packages/client/classic-environment-v2/src/lib/error-envelopes/index.d.ts

@@ -0,0 +1,6 @@
+export { isClientRequestError } from './client-request-error';
+export { isApiClientError } from './api-client-error';
+export { isErrorEnvelopeError } from './error-envelope-error';
+export { isValidationResponseError } from './validation-response-error';
+export { isSettingsObjectResponseError } from './settings-object-response-error';
+export { isSettingsObjectResponseArrayError } from './settings-object-response-array-error';

package/types/packages/client/classic-environment-v2/src/lib/error-envelopes/settings-object-response-array-error.d.ts

@@ -0,0 +1,8 @@
+/**
+ * SettingsObjectResponse[]
+ */
+import { ClientRequestError } from './client-request-error';
+import { SettingsObjectResponse } from '../models';
+export declare class SettingsObjectResponseArrayError extends ClientRequestError<SettingsObjectResponse[]> {
+}
+export declare function isSettingsObjectResponseArrayError(e: any): e is SettingsObjectResponseArrayError;

package/types/packages/client/classic-environment-v2/src/lib/error-envelopes/settings-object-response-error.d.ts

@@ -0,0 +1,8 @@
+/**
+ * SettingsObjectResponse
+ */
+import { ClientRequestError } from './client-request-error';
+import { SettingsObjectResponse } from '../models';
+export declare class SettingsObjectResponseError extends ClientRequestError<SettingsObjectResponse> {
+}
+export declare function isSettingsObjectResponseError(e: any): e is SettingsObjectResponseError;

package/types/packages/client/classic-environment-v2/src/lib/error-envelopes/validation-response-error.d.ts

@@ -0,0 +1,8 @@
+/**
+ * ValidationResponse
+ */
+import { ClientRequestError } from './client-request-error';
+import { ValidationResponse } from '../models';
+export declare class ValidationResponseError extends ClientRequestError<ValidationResponse> {
+}
+export declare function isValidationResponseError(e: any): e is ValidationResponseError;

package/types/packages/client/classic-environment-v2/src/lib/index.d.ts

@@ -0,0 +1,3 @@
+export * from './apis';
+export * from './error-envelopes';
+export * from './models';

package/types/packages/client/classic-environment-v2/src/lib/models/abstract-credentials-response-element-scope.d.ts

@@ -0,0 +1,15 @@
+/**
+ * The scope of the credentials set.
+ */
+export declare enum AbstractCredentialsResponseElementScope {
+    All = "ALL",
+    Extension = "EXTENSION",
+    Synthetic = "SYNTHETIC",
+    Unknown = "UNKNOWN"
+}
+/** @ignore */
+export declare namespace _AbstractCredentialsResponseElementScopeTransformation {
+    type AsJson = AbstractCredentialsResponseElementScope;
+    const toJson: (value: AbstractCredentialsResponseElementScope) => AsJson;
+    const fromJson: (value: AsJson) => AbstractCredentialsResponseElementScope;
+}

package/types/packages/client/classic-environment-v2/src/lib/models/abstract-credentials-response-element-type.d.ts

@@ -0,0 +1,20 @@
+/**
+ * Defines the actual set of fields depending on the value. See one of the following objects:
+ *
+ * * `USERNAME_PASSWORD` -> CredentialsDetailsUsernamePasswordResponseElement
+ * * `CERTIFICATE` -> CredentialsDetailsCertificateResponseElement
+ * * `TOKEN` -> CredentialsDetailsTokenResponseElement
+ * * `PUBLIC_CERTIFICATE` -> CredentialsDetailsCertificateResponseElement
+ */
+export declare enum AbstractCredentialsResponseElementType {
+    Certificate = "CERTIFICATE",
+    PublicCertificate = "PUBLIC_CERTIFICATE",
+    Token = "TOKEN",
+    UsernamePassword = "USERNAME_PASSWORD"
+}
+/** @ignore */
+export declare namespace _AbstractCredentialsResponseElementTypeTransformation {
+    type AsJson = AbstractCredentialsResponseElementType;
+    const toJson: (value: AbstractCredentialsResponseElementType) => AsJson;
+    const fromJson: (value: AsJson) => AbstractCredentialsResponseElementType;
+}

package/types/packages/client/classic-environment-v2/src/lib/models/abstract-credentials-response-element.d.ts

@@ -0,0 +1,58 @@
+import { AbstractCredentialsResponseElementScope, _AbstractCredentialsResponseElementScopeTransformation } from './abstract-credentials-response-element-scope';
+import { AbstractCredentialsResponseElementType, _AbstractCredentialsResponseElementTypeTransformation } from './abstract-credentials-response-element-type';
+import { CredentialUsageHandler, _CredentialUsageHandlerTransformation } from './credential-usage-handler';
+import { CredentialsDetailsCertificateResponseElement } from './credentials-details-certificate-response-element';
+import { CredentialsDetailsTokenResponseElement } from './credentials-details-token-response-element';
+import { CredentialsDetailsUsernamePasswordResponseElement } from './credentials-details-username-password-response-element';
+import { ExternalVaultConfig, _ExternalVaultConfigTransformation } from './external-vault-config';
+/**
+ * Credentials set.
+ */
+export interface AbstractCredentialsResponseElement {
+    /**
+     * The name of the credentials set.
+     */
+    name: string;
+    /**
+     * The ID of the credentials set.
+     */
+    id?: string;
+    /**
+     * A short description of the credentials set.
+     */
+    description: string;
+    /**
+     * The owner of the credential (user for which used API token was created).
+     */
+    owner: string;
+    /**
+     * Flag indicating that this credential is visible only to the owner.
+     */
+    ownerAccessOnly: boolean;
+    scope?: AbstractCredentialsResponseElementScope;
+    externalVault?: ExternalVaultConfig;
+    /**
+     * The list contains summary data related to the use of credentials.
+     */
+    credentialUsageSummary: CredentialUsageHandler[];
+    type: AbstractCredentialsResponseElementType;
+}
+/** @ignore */
+export declare namespace _AbstractCredentialsResponseElementTransformation {
+    function isCredentialsDetailsUsernamePasswordResponseElement(model: AbstractCredentialsResponseElement): model is CredentialsDetailsUsernamePasswordResponseElement;
+    function isCredentialsDetailsCertificateResponseElement(model: AbstractCredentialsResponseElement): model is CredentialsDetailsCertificateResponseElement;
+    function isCredentialsDetailsTokenResponseElement(model: AbstractCredentialsResponseElement): model is CredentialsDetailsTokenResponseElement;
+    interface AsJson {
+        name: string;
+        id?: string;
+        description: string;
+        owner: string;
+        ownerAccessOnly: boolean;
+        scope?: _AbstractCredentialsResponseElementScopeTransformation.AsJson;
+        externalVault?: _ExternalVaultConfigTransformation.AsJson;
+        credentialUsageSummary: _CredentialUsageHandlerTransformation.AsJson[];
+        type: _AbstractCredentialsResponseElementTypeTransformation.AsJson;
+    }
+    function fromJson(model: AsJson, includeChildProps?: boolean): AbstractCredentialsResponseElement;
+    function toJson(model: AbstractCredentialsResponseElement, includeChildProps?: boolean): AsJson;
+}