npm - qovery-typescript-axios - Versions diffs - 1.1.1022 → 1.1.1024 - Mend

qovery-typescript-axios 1.1.1022 → 1.1.1024

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (6) hide show

package/api.ts CHANGED Viewed

@@ -26307,13 +26307,13 @@ export interface SecretResponseList {
     'results'?: Array<Secret>;
 }
 /**
- * AWS cloud credential of the organization that the cluster runs on. This operation only takes and returns its id.
+ * Cloud credential of the organization that the cluster runs on, of the same provider as the cluster. This operation only takes and returns its id.
  * @export
  * @interface SelfManagedClusterCredentials
  */
 export interface SelfManagedClusterCredentials {
     /**
-     * Id of an existing AWS cloud credential of the organization
+     * Id of an existing cloud credential of the organization
      * @type {string}
      * @memberof SelfManagedClusterCredentials
      */
@@ -26369,7 +26369,7 @@ export interface SelfManagedClusterPlatformSelection {
     'managedConfig'?: { [key: string]: { [key: string]: any; }; };
 }
 /**
- * Default ECR registry of the cluster, derived from its cloud credential and region.
+ * Default registry of the cluster, derived from its cloud credential and region: ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway.
  * @export
  * @interface SelfManagedClusterRegistryResponse
  */
@@ -26408,13 +26408,13 @@ export interface SelfManagedClusterRequest {
      */
     'production'?: boolean;
     /**
-     *
+     * Cloud provider of the cluster. The cluster kind is EKS_SELF_MANAGED on AWS, GKE_SELF_MANAGED on GCP and SCW_SELF_MANAGED on SCW.
      * @type {string}
      * @memberof SelfManagedClusterRequest
      */
     'provider': SelfManagedClusterRequestProviderEnum;
     /**
-     *
+     * Region of the provider known to Qovery; a zone such as `fr-par-1` on Scaleway.
      * @type {string}
      * @memberof SelfManagedClusterRequest
      */
@@ -26440,7 +26440,9 @@ export interface SelfManagedClusterRequest {
 }
 export const SelfManagedClusterRequestProviderEnum = {
-    AWS: 'AWS'
+    AWS: 'AWS',
+    GCP: 'GCP',
+    SCW: 'SCW'
 } as const;
 export type SelfManagedClusterRequestProviderEnum = typeof SelfManagedClusterRequestProviderEnum[keyof typeof SelfManagedClusterRequestProviderEnum];
@@ -29916,6 +29918,12 @@ export interface WidePermissionsRequestDto {
      * @memberof WidePermissionsRequestDto
      */
     'wide_scope_cloud_account_id'?: string | null;
+    /**
+     *
+     * @type {string}
+     * @memberof WidePermissionsRequestDto
+     */
+    'slack_webhook_url'?: string | null;
 }
 /**
  *
@@ -29941,6 +29949,12 @@ export interface WidePermissionsResponseDto {
      * @memberof WidePermissionsResponseDto
      */
     'require_wide_access_to_deploy'?: boolean;
+    /**
+     *
+     * @type {string}
+     * @memberof WidePermissionsResponseDto
+     */
+    'slack_webhook_url'?: string | null;
 }
 /**
@@ -43512,7 +43526,7 @@ export const ClustersApiAxiosParamCreator = function (configuration?: Configurat
             };
         },
         /**
-         * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+         * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
          * @summary Create a self-managed cluster run by the Qovery Operator
          * @param {string} organizationId Organization ID
          * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -45378,7 +45392,7 @@ export const ClustersApiFp = function(configuration?: Configuration) {
             return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
         },
         /**
-         * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+         * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
          * @summary Create a self-managed cluster run by the Qovery Operator
          * @param {string} organizationId Organization ID
          * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -45948,7 +45962,7 @@ export const ClustersApiFactory = function (configuration?: Configuration, baseP
             return localVarFp.createCluster(organizationId, clusterRequest, options).then((request) => request(axios, basePath));
         },
         /**
-         * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+         * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
          * @summary Create a self-managed cluster run by the Qovery Operator
          * @param {string} organizationId Organization ID
          * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -46409,7 +46423,7 @@ export class ClustersApi extends BaseAPI {
     }
     /**
-     * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+     * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
      * @summary Create a self-managed cluster run by the Qovery Operator
      * @param {string} organizationId Organization ID
      * @param {SelfManagedClusterRequest} selfManagedClusterRequest

package/dist/api.d.ts CHANGED Viewed

@@ -25543,13 +25543,13 @@ export interface SecretResponseList {
     'results'?: Array<Secret>;
 }
 /**
- * AWS cloud credential of the organization that the cluster runs on. This operation only takes and returns its id.
+ * Cloud credential of the organization that the cluster runs on, of the same provider as the cluster. This operation only takes and returns its id.
  * @export
  * @interface SelfManagedClusterCredentials
  */
 export interface SelfManagedClusterCredentials {
     /**
-     * Id of an existing AWS cloud credential of the organization
+     * Id of an existing cloud credential of the organization
      * @type {string}
      * @memberof SelfManagedClusterCredentials
      */
@@ -25607,7 +25607,7 @@ export interface SelfManagedClusterPlatformSelection {
     };
 }
 /**
- * Default ECR registry of the cluster, derived from its cloud credential and region.
+ * Default registry of the cluster, derived from its cloud credential and region: ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway.
  * @export
  * @interface SelfManagedClusterRegistryResponse
  */
@@ -25644,13 +25644,13 @@ export interface SelfManagedClusterRequest {
      */
     'production'?: boolean;
     /**
-     *
+     * Cloud provider of the cluster. The cluster kind is EKS_SELF_MANAGED on AWS, GKE_SELF_MANAGED on GCP and SCW_SELF_MANAGED on SCW.
      * @type {string}
      * @memberof SelfManagedClusterRequest
      */
     'provider': SelfManagedClusterRequestProviderEnum;
     /**
-     *
+     * Region of the provider known to Qovery; a zone such as `fr-par-1` on Scaleway.
      * @type {string}
      * @memberof SelfManagedClusterRequest
      */
@@ -25680,6 +25680,8 @@ export interface SelfManagedClusterRequest {
 }
 export declare const SelfManagedClusterRequestProviderEnum: {
     readonly AWS: "AWS";
+    readonly GCP: "GCP";
+    readonly SCW: "SCW";
 };
 export type SelfManagedClusterRequestProviderEnum = typeof SelfManagedClusterRequestProviderEnum[keyof typeof SelfManagedClusterRequestProviderEnum];
 /**
@@ -29024,6 +29026,12 @@ export interface WidePermissionsRequestDto {
      * @memberof WidePermissionsRequestDto
      */
     'wide_scope_cloud_account_id'?: string | null;
+    /**
+     *
+     * @type {string}
+     * @memberof WidePermissionsRequestDto
+     */
+    'slack_webhook_url'?: string | null;
 }
 /**
  *
@@ -29049,6 +29057,12 @@ export interface WidePermissionsResponseDto {
      * @memberof WidePermissionsResponseDto
      */
     'require_wide_access_to_deploy'?: boolean;
+    /**
+     *
+     * @type {string}
+     * @memberof WidePermissionsResponseDto
+     */
+    'slack_webhook_url'?: string | null;
 }
 /**
  * AccountInfoApi - axios parameter creator
@@ -35227,7 +35241,7 @@ export declare const ClustersApiAxiosParamCreator: (configuration?: Configuratio
      */
     createCluster: (organizationId: string, clusterRequest?: ClusterRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+     * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
      * @summary Create a self-managed cluster run by the Qovery Operator
      * @param {string} organizationId Organization ID
      * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -35606,7 +35620,7 @@ export declare const ClustersApiFp: (configuration?: Configuration) => {
      */
     createCluster(organizationId: string, clusterRequest?: ClusterRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Cluster>>;
     /**
-     * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+     * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
      * @summary Create a self-managed cluster run by the Qovery Operator
      * @param {string} organizationId Organization ID
      * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -35985,7 +35999,7 @@ export declare const ClustersApiFactory: (configuration?: Configuration, basePat
      */
     createCluster(organizationId: string, clusterRequest?: ClusterRequest, options?: RawAxiosRequestConfig): AxiosPromise<Cluster>;
     /**
-     * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+     * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
      * @summary Create a self-managed cluster run by the Qovery Operator
      * @param {string} organizationId Organization ID
      * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -36367,7 +36381,7 @@ export declare class ClustersApi extends BaseAPI {
      */
     createCluster(organizationId: string, clusterRequest?: ClusterRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<Cluster, any, {}, any>>;
     /**
-     * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+     * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
      * @summary Create a self-managed cluster run by the Qovery Operator
      * @param {string} organizationId Organization ID
      * @param {SelfManagedClusterRequest} selfManagedClusterRequest

package/dist/api.js CHANGED Viewed

@@ -1563,7 +1563,9 @@ exports.SelfManagedClusterKind = {
     SELF_MANAGED: 'SELF_MANAGED'
 };
 exports.SelfManagedClusterRequestProviderEnum = {
-    AWS: 'AWS'
+    AWS: 'AWS',
+    GCP: 'GCP',
+    SCW: 'SCW'
 };
 /**
  *
@@ -14509,7 +14511,7 @@ const ClustersApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+         * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
          * @summary Create a self-managed cluster run by the Qovery Operator
          * @param {string} organizationId Organization ID
          * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -16072,7 +16074,7 @@ const ClustersApiFp = function (configuration) {
             });
         },
         /**
-         * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+         * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
          * @summary Create a self-managed cluster run by the Qovery Operator
          * @param {string} organizationId Organization ID
          * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -16753,7 +16755,7 @@ const ClustersApiFactory = function (configuration, basePath, axios) {
             return localVarFp.createCluster(organizationId, clusterRequest, options).then((request) => request(axios, basePath));
         },
         /**
-         * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+         * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
          * @summary Create a self-managed cluster run by the Qovery Operator
          * @param {string} organizationId Organization ID
          * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -17213,7 +17215,7 @@ class ClustersApi extends base_1.BaseAPI {
         return (0, exports.ClustersApiFp)(this.configuration).createCluster(organizationId, clusterRequest, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+     * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
      * @summary Create a self-managed cluster run by the Qovery Operator
      * @param {string} organizationId Organization ID
      * @param {SelfManagedClusterRequest} selfManagedClusterRequest

package/dist/esm/api.d.ts CHANGED Viewed

@@ -25543,13 +25543,13 @@ export interface SecretResponseList {
     'results'?: Array<Secret>;
 }
 /**
- * AWS cloud credential of the organization that the cluster runs on. This operation only takes and returns its id.
+ * Cloud credential of the organization that the cluster runs on, of the same provider as the cluster. This operation only takes and returns its id.
  * @export
  * @interface SelfManagedClusterCredentials
  */
 export interface SelfManagedClusterCredentials {
     /**
-     * Id of an existing AWS cloud credential of the organization
+     * Id of an existing cloud credential of the organization
      * @type {string}
      * @memberof SelfManagedClusterCredentials
      */
@@ -25607,7 +25607,7 @@ export interface SelfManagedClusterPlatformSelection {
     };
 }
 /**
- * Default ECR registry of the cluster, derived from its cloud credential and region.
+ * Default registry of the cluster, derived from its cloud credential and region: ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway.
  * @export
  * @interface SelfManagedClusterRegistryResponse
  */
@@ -25644,13 +25644,13 @@ export interface SelfManagedClusterRequest {
      */
     'production'?: boolean;
     /**
-     *
+     * Cloud provider of the cluster. The cluster kind is EKS_SELF_MANAGED on AWS, GKE_SELF_MANAGED on GCP and SCW_SELF_MANAGED on SCW.
      * @type {string}
      * @memberof SelfManagedClusterRequest
      */
     'provider': SelfManagedClusterRequestProviderEnum;
     /**
-     *
+     * Region of the provider known to Qovery; a zone such as `fr-par-1` on Scaleway.
      * @type {string}
      * @memberof SelfManagedClusterRequest
      */
@@ -25680,6 +25680,8 @@ export interface SelfManagedClusterRequest {
 }
 export declare const SelfManagedClusterRequestProviderEnum: {
     readonly AWS: "AWS";
+    readonly GCP: "GCP";
+    readonly SCW: "SCW";
 };
 export type SelfManagedClusterRequestProviderEnum = typeof SelfManagedClusterRequestProviderEnum[keyof typeof SelfManagedClusterRequestProviderEnum];
 /**
@@ -29024,6 +29026,12 @@ export interface WidePermissionsRequestDto {
      * @memberof WidePermissionsRequestDto
      */
     'wide_scope_cloud_account_id'?: string | null;
+    /**
+     *
+     * @type {string}
+     * @memberof WidePermissionsRequestDto
+     */
+    'slack_webhook_url'?: string | null;
 }
 /**
  *
@@ -29049,6 +29057,12 @@ export interface WidePermissionsResponseDto {
      * @memberof WidePermissionsResponseDto
      */
     'require_wide_access_to_deploy'?: boolean;
+    /**
+     *
+     * @type {string}
+     * @memberof WidePermissionsResponseDto
+     */
+    'slack_webhook_url'?: string | null;
 }
 /**
  * AccountInfoApi - axios parameter creator
@@ -35227,7 +35241,7 @@ export declare const ClustersApiAxiosParamCreator: (configuration?: Configuratio
      */
     createCluster: (organizationId: string, clusterRequest?: ClusterRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+     * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
      * @summary Create a self-managed cluster run by the Qovery Operator
      * @param {string} organizationId Organization ID
      * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -35606,7 +35620,7 @@ export declare const ClustersApiFp: (configuration?: Configuration) => {
      */
     createCluster(organizationId: string, clusterRequest?: ClusterRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Cluster>>;
     /**
-     * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+     * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
      * @summary Create a self-managed cluster run by the Qovery Operator
      * @param {string} organizationId Organization ID
      * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -35985,7 +35999,7 @@ export declare const ClustersApiFactory: (configuration?: Configuration, basePat
      */
     createCluster(organizationId: string, clusterRequest?: ClusterRequest, options?: RawAxiosRequestConfig): AxiosPromise<Cluster>;
     /**
-     * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+     * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
      * @summary Create a self-managed cluster run by the Qovery Operator
      * @param {string} organizationId Organization ID
      * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -36367,7 +36381,7 @@ export declare class ClustersApi extends BaseAPI {
      */
     createCluster(organizationId: string, clusterRequest?: ClusterRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<Cluster, any, {}, any>>;
     /**
-     * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+     * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
      * @summary Create a self-managed cluster run by the Qovery Operator
      * @param {string} organizationId Organization ID
      * @param {SelfManagedClusterRequest} selfManagedClusterRequest

package/dist/esm/api.js CHANGED Viewed

@@ -1548,7 +1548,9 @@ export const SelfManagedClusterKind = {
     SELF_MANAGED: 'SELF_MANAGED'
 };
 export const SelfManagedClusterRequestProviderEnum = {
-    AWS: 'AWS'
+    AWS: 'AWS',
+    GCP: 'GCP',
+    SCW: 'SCW'
 };
 /**
  *
@@ -14406,7 +14408,7 @@ export const ClustersApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+         * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
          * @summary Create a self-managed cluster run by the Qovery Operator
          * @param {string} organizationId Organization ID
          * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -15968,7 +15970,7 @@ export const ClustersApiFp = function (configuration) {
             });
         },
         /**
-         * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+         * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
          * @summary Create a self-managed cluster run by the Qovery Operator
          * @param {string} organizationId Organization ID
          * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -16648,7 +16650,7 @@ export const ClustersApiFactory = function (configuration, basePath, axios) {
             return localVarFp.createCluster(organizationId, clusterRequest, options).then((request) => request(axios, basePath));
         },
         /**
-         * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+         * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
          * @summary Create a self-managed cluster run by the Qovery Operator
          * @param {string} organizationId Organization ID
          * @param {SelfManagedClusterRequest} selfManagedClusterRequest
@@ -17107,7 +17109,7 @@ export class ClustersApi extends BaseAPI {
         return ClustersApiFp(this.configuration).createCluster(organizationId, clusterRequest, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Creates a self-managed cluster on an existing AWS cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. The credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its ECR access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default ECR registry derived from the credential, its initial deployment status, its platform configuration and its Qovery Operator enrollment. Only the AWS provider is supported. Install the Operator next with the cluster\'s Operator bootstrap.
+     * Creates a self-managed cluster on an existing AWS, GCP or Scaleway cloud credential of the organization. The organization\'s plan must include self-managed clusters, otherwise the call answers 403. On AWS the credential only needs ECR permissions for the cluster itself, including `ecr:DescribeRepositories` in `us-east-1`, which Qovery calls to check the credential whatever the cluster region; features that call other AWS services with the credential, such as managed databases or Terraform services using the cluster credentials, need more. Without `platform.templateKey` and `platform.templateVersion`, Qovery selects its self-managed platform template release and the response returns it: `\"platform\": {}` gives that release with its default configuration. Without `clusterInputs`, the cluster has no cluster inputs. The credential, including its registry access in the cluster region, and the platform configuration are checked before anything is created. One transaction then writes the cluster, its Qovery DNS and build providers, its default registry derived from the credential (ECR on AWS, Artifact Registry on GCP, Scaleway Container Registry on Scaleway), its initial deployment status, its platform configuration and its Qovery Operator enrollment. Install the Operator next with the cluster\'s Operator bootstrap.
      * @summary Create a self-managed cluster run by the Qovery Operator
      * @param {string} organizationId Organization ID
      * @param {SelfManagedClusterRequest} selfManagedClusterRequest

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "qovery-typescript-axios",
-  "version": "v1.1.1022",
+  "version": "v1.1.1024",
   "description": "OpenAPI client for qovery-typescript-axios",
   "author": "OpenAPI-Generator Contributors",
   "repository": {