@northflank/js-client 0.7.1-beta.0 → 0.7.2

package/dist/cjs/api-client.d.ts

@@ -59,6 +59,7 @@ declare type PortForwardingInfo = {
     portName?: string;
     protocol?: 'HTTP' | 'TCP' | 'UDP';
     hostnames: string[];
+    ipOnly: boolean;
 };
 interface PortTunnel extends EventEmitter {
     readonly bindTo?: {
@@ -211,7 +212,7 @@ declare type ListServicesResult = {
             /** Details about the current deployment status. */
             'deployment'?: {
                 /** The current status of the deployment. Example: "COMPLETED" */
-                'status': 'IN_PROGRESS' | 'COMPLETED';
+                'status': 'PENDING' | 'IN_PROGRESS' | 'COMPLETED' | 'FAILED';
                 /** The reason the current deployment was started. Example: "DEPLOYING" */
                 'reason': 'SCALING' | 'DEPLOYING';
                 /** The timestamp of when the deployment reached this status. Example: "2021-11-29T11:47:16.624Z" */
@@ -747,6 +748,10 @@ declare type CreateAddonData = {
     }[];
     /** Enables point-in-time recovery (PITR) for the addon (if supported by the addon type). */
     'pitrEnabled'?: boolean;
+    'typeSpecificSettings'?: {
+        /** Postgres only: enable high-availability mode. */
+        'postgresHAEnabled'?: boolean;
+    };
 };
 /** Creates a new addon */
 declare class CreateAddonEndpoint extends PostApiEndpoint<CreateAddonRequest, CreateAddonResult> {
@@ -796,6 +801,10 @@ declare type PutAddonResult = {
     }[];
     /** Enables point-in-time recovery (PITR) for the addon (if supported by the addon type). */
     'pitrEnabled'?: boolean;
+    'typeSpecificSettings'?: {
+        /** Postgres only: enable high-availability mode. */
+        'postgresHAEnabled'?: boolean;
+    };
     /** Identifier for the addon. Example: "example-addon" */
     'id': string;
     /** Full identifier used for deployment Example: "/example-user/default-project/example-addon" */
@@ -854,6 +863,10 @@ declare type PutAddonData = {
     }[];
     /** Enables point-in-time recovery (PITR) for the addon (if supported by the addon type). */
     'pitrEnabled'?: boolean;
+    'typeSpecificSettings'?: {
+        /** Postgres only: enable high-availability mode. */
+        'postgresHAEnabled'?: boolean;
+    };
 };
 /** Creates or updates an addon */
 declare class PutAddonEndpoint extends PutApiEndpoint<PutAddonRequest, PutAddonResult> {
@@ -974,6 +987,10 @@ declare type PatchAddonResult = {
     }[];
     /** Enables point-in-time recovery (PITR) for the addon (if supported by the addon type). */
     'pitrEnabled'?: boolean;
+    'typeSpecificSettings'?: {
+        /** Postgres only: enable high-availability mode. */
+        'postgresHAEnabled'?: boolean;
+    };
     /** Identifier for the addon. Example: "example-addon" */
     'id': string;
     /** Full identifier used for deployment Example: "/example-user/default-project/example-addon" */
@@ -2488,9 +2505,9 @@ declare type CreateClusterData = {
     'description'?: string;
     /** Cloud provider to be used for the selected resource Example: "gcp" */
     'provider': 'gcp' | 'aws' | 'azure' | 'do';
-    /** Region of the cluster. */
+    /** Region of the cluster. Example: "europe-west2" */
     'region': string;
-    /** Kubernetes version of the cluster. */
+    /** Kubernetes version of the cluster. Example: "1.23.8" */
     'kubernetesVersion': string;
     /** Existing integration to use for this cluster. Example: "gcp-integration" */
     'integrationId'?: string;
@@ -2528,9 +2545,40 @@ declare type CreateClusterData = {
         /** Zones in which the node pool should be provisioned. */
         'availabilityZones'?: string[];
     }[];
+    'settings': {
+        /** Determines if builds are run on Northflank infrastructure */
+        'useNorthflankBuilder'?: boolean;
+        'builds'?: {
+            /** Plan to use for builds if they are run on the cluster Example: "nf-compute-200" */
+            'plan'?: string;
+        };
+        /** Request modifiers to use for different resources. */
+        'requestModifiers'?: {
+            /** Request modifiers for services */
+            'services'?: {
+                'cpu': number;
+                'memory': number;
+            };
+            /** Request modifiers for jobs */
+            'jobs'?: {
+                'cpu': number;
+                'memory': number;
+            };
+            /** Request modifiers for builds */
+            'builds'?: {
+                'cpu': number;
+                'memory': number;
+            };
+            /** Request modifiers for addons */
+            'addons'?: {
+                'cpu': number;
+                'memory': number;
+            };
+        };
+    };
     /** GCP specific data. Required when `provider` is `gcp`. */
     'gcp'?: {
-        /** ID of the GCP project the cluster will be provisioned in. */
+        /** ID of the GCP project the cluster will be provisioned in. Example: "example-project-id" */
         'projectId': string;
     };
 };
@@ -2664,7 +2712,7 @@ declare type UpdateClusterParameters = {
 declare type UpdateClusterData = {
     /** The description of the cluster. Example: "This is an updated description." */
     'description'?: string;
-    'nodePools': {
+    'nodePools'?: {
         /** Machine type to be used by the node pool. Example: "n2-standard-8" */
         'nodeType': string;
         /** Number of nodes to the node pool should be provisioned with. Example: 3 */
@@ -2688,6 +2736,37 @@ declare type UpdateClusterData = {
         /** ID of existing node pool. Must be passed when modifying existing node pools. Not relevant for new node pools Example: "6aa96121-0345-43ad-bade-af36d540c222" */
         'id'?: string;
     }[];
+    'settings'?: {
+        /** Determines if builds are run on Northflank infrastructure */
+        'useNorthflankBuilder'?: boolean;
+        'builds'?: {
+            /** Plan to use for builds if they are run on the cluster Example: "nf-compute-200" */
+            'plan'?: string;
+        };
+        /** Request modifiers to use for different resources. */
+        'requestModifiers'?: {
+            /** Request modifiers for services */
+            'services'?: {
+                'cpu': number;
+                'memory': number;
+            };
+            /** Request modifiers for jobs */
+            'jobs'?: {
+                'cpu': number;
+                'memory': number;
+            };
+            /** Request modifiers for builds */
+            'builds'?: {
+                'cpu': number;
+                'memory': number;
+            };
+            /** Request modifiers for addons */
+            'addons'?: {
+                'cpu': number;
+                'memory': number;
+            };
+        };
+    };
 };
 /** Update an existing cluster. */
 declare class UpdateClusterEndpoint extends PostApiEndpoint<UpdateClusterRequest, UpdateClusterResult> {
@@ -2795,6 +2874,12 @@ declare type GetJobResult = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -2949,6 +3034,12 @@ declare type CreateJobManualResult = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -3169,6 +3260,12 @@ declare type CreateJobManualData = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -3180,12 +3277,12 @@ declare type CreateJobManualData = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -3314,6 +3411,12 @@ declare type PutJobManualResult = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -3325,12 +3428,12 @@ declare type PutJobManualResult = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -3533,6 +3636,12 @@ declare type PutJobManualData = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -3544,12 +3653,12 @@ declare type PutJobManualData = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -3678,6 +3787,12 @@ declare type PatchJobManualResult = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -3689,12 +3804,12 @@ declare type PatchJobManualResult = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -3786,17 +3901,23 @@ declare type PatchJobManualData = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
     };
     'buildSettings'?: {
         'dockerfile'?: {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath'?: string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir'?: string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
         'buildpack'?: {
             /** Buildpack stack to use. Defaults to recommended stack `HEROKU_22_CLASSIC`. Example: "HEROKU_22_CLASSIC" */
@@ -3882,6 +4003,12 @@ declare type CreateJobCronResult = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -4108,6 +4235,12 @@ declare type CreateJobCronData = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -4119,12 +4252,12 @@ declare type CreateJobCronData = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -4257,6 +4390,12 @@ declare type PutJobCronResult = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -4268,12 +4407,12 @@ declare type PutJobCronResult = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -4480,6 +4619,12 @@ declare type PutJobCronData = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -4491,12 +4636,12 @@ declare type PutJobCronData = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -4629,6 +4774,12 @@ declare type PatchJobCronResult = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -4640,12 +4791,12 @@ declare type PatchJobCronResult = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -4741,17 +4892,23 @@ declare type PatchJobCronData = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
     };
     'buildSettings'?: {
         'dockerfile'?: {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath'?: string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir'?: string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
         'buildpack'?: {
             /** Buildpack stack to use. Defaults to recommended stack `HEROKU_22_CLASSIC`. Example: "HEROKU_22_CLASSIC" */
@@ -5441,6 +5598,12 @@ declare type UpdateJobBuildoptionsData = {
     };
     /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
     'pathIgnoreRules'?: string[];
+    /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+    'isAllowList'?: boolean;
+    /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+    'ciIgnoreFlagsEnabled'?: boolean;
+    /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+    'ciIgnoreFlags'?: string[];
     /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
     'dockerfileTarget'?: string;
     /** Include .git folder inside the build context */
@@ -5460,9 +5623,21 @@ declare type UpdateJobBuildoptionsData = {
     };
     /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
     'pathIgnoreRules'?: string[];
+    /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+    'isAllowList'?: boolean;
+    /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+    'ciIgnoreFlagsEnabled'?: boolean;
+    /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+    'ciIgnoreFlags'?: string[];
 } | {
     /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
     'pathIgnoreRules'?: string[];
+    /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+    'isAllowList'?: boolean;
+    /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+    'ciIgnoreFlagsEnabled'?: boolean;
+    /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+    'ciIgnoreFlags'?: string[];
     /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
     'dockerfileTarget'?: string;
     /** Include .git folder inside the build context */
@@ -6106,6 +6281,8 @@ declare type ListLogsinksResult = {
     'logSinks': {
         /** Name of the log sink. Example: "example-log-sink" */
         'name': string;
+        /** Identifier for the Log Sink Example: "example-project" */
+        'id': string;
         /** Description of the log sink. Example: "This is an example log sink." */
         'description'?: string;
         /** If `true`, only logs from the projects in `projects` will be sent to the log sink. Example: true */
@@ -6371,6 +6548,8 @@ declare class CreateLogsinkEndpoint extends PostApiEndpoint<CreateLogsinkRequest
 declare type GetLogsinkResult = {
     /** Name of the log sink. Example: "example-log-sink" */
     'name': string;
+    /** Identifier for the Log Sink Example: "example-project" */
+    'id': string;
     /** Description of the log sink. Example: "This is an example log sink." */
     'description'?: string;
     /** If `true`, only logs from the projects in `projects` will be sent to the log sink. Example: true */
@@ -6406,7 +6585,58 @@ declare type GetLogsinkResult = {
         'default_api_key': string;
         /** The Datadog region. Example: "eu" */
         'region': 'eu' | 'us' | 'us3' | 'us5';
-    } | any;
+    } | any | {
+        /** Uri to send logs to. Example: "my.log-collector.com" */
+        'uri': string;
+        /** Encoding options */
+        'encoding'?: {
+            /** Codec to encode logs in Example: "json" */
+            'codec': 'text' | 'json';
+        };
+        'auth': {
+            /** No authentication strategy Example: "none" */
+            'strategy': 'none';
+        } | {
+            /** Basic HTTP authentication strategy. Example: "basic" */
+            'strategy': 'basic';
+            /** Username for basic http authentication. Example: "my-user" */
+            'user'?: string;
+            /** Password for basic http authentication. Example: "secret-password" */
+            'password': string;
+        } | {
+            /** Bearer token authentication strategy. Example: "bearer" */
+            'strategy': 'bearer';
+            /** Token for bearer token authentication. Example: "my-token" */
+            'token'?: string;
+        };
+    } | {
+        /** Endpoint for the AWS S3 or compatible API bucket. Example: "my.bucket.com" */
+        'endpoint': string;
+        /** Region of the S3 bucket. Example: "eu-west-2" */
+        'region': 'eu-west-1' | 'eu-west-2' | 'eu-west-3' | 'eu-central-1' | 'eu-south-1' | 'eu-north-1' | 'us-west-1' | 'us-west-2' | 'us-east-1' | 'us-east2';
+        /** Authentication object. */
+        'auth'?: {
+            /** Access key id for the bucket. Example: "PMSACIHNUIASDBWQDS" */
+            'accessKeyId': string;
+            /** Secret access key for the bucket. Example: "HA1PLMNOEAEYUHAJQMSDUJQS" */
+            'secretAccessKey': string;
+        };
+        /** Name of the S3 Bucket. Example: "northflank-logs" */
+        'bucket': string;
+        /** Log file compression method. Example: "gzip" */
+        'compression': 'gzip' | 'none';
+    } | {
+        /** Logtail Source Token Example: "vhnqrLygVQ5GnSQUTZamKvAq" */
+        'token': string;
+    } | {
+        /** Ingestion Key Example: "b1dd3feb585asd1a3e9edpo9kmn5e590hg9" */
+        'api_key': string;
+    } | {
+        /** Honeycomb API Key Example: "b1dd3feb585asd1a3e9" */
+        'api_key': string;
+        /** Name of the dataset Example: "staging-logs" */
+        'dataset': string;
+    };
 };
 declare type GetLogsinkCall = (opts: GetLogsinkRequest) => Promise<ApiCallResponse<GetLogsinkResult>>;
 declare type GetLogsinkRequest = {
@@ -7866,7 +8096,7 @@ declare type CreateServiceCombinedResult = {
         /** Details about the current deployment status. */
         'deployment'?: {
             /** The current status of the deployment. Example: "COMPLETED" */
-            'status': 'IN_PROGRESS' | 'COMPLETED';
+            'status': 'PENDING' | 'IN_PROGRESS' | 'COMPLETED' | 'FAILED';
             /** The reason the current deployment was started. Example: "DEPLOYING" */
             'reason': 'SCALING' | 'DEPLOYING';
             /** The timestamp of when the deployment reached this status. Example: "2021-11-29T11:47:16.624Z" */
@@ -7944,6 +8174,12 @@ declare type CreateServiceCombinedResult = {
     'buildConfiguration': {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -8025,6 +8261,10 @@ declare type CreateServiceCombinedData = {
                 'storageSize'?: number;
             };
         };
+        'strategy'?: {
+            /** Configures the instance roll out strategy of your service. Currently only available via feature flag. */
+            'type'?: 'recreate' | 'rollout-steady' | 'rollout-balanced' | 'rollout-fast';
+        };
     };
     'ports'?: {
         /** The name used to identify the port. Example: "port-1" */
@@ -8074,12 +8314,12 @@ declare type CreateServiceCombinedData = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -8096,6 +8336,12 @@ declare type CreateServiceCombinedData = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -8182,6 +8428,10 @@ declare type PutServiceCombinedResult = {
                 'storageSize'?: number;
             };
         };
+        'strategy'?: {
+            /** Configures the instance roll out strategy of your service. Currently only available via feature flag. */
+            'type'?: 'recreate' | 'rollout-steady' | 'rollout-balanced' | 'rollout-fast';
+        };
     };
     'ports'?: {
         /** The name used to identify the port. Example: "port-1" */
@@ -8231,12 +8481,12 @@ declare type PutServiceCombinedResult = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -8253,6 +8503,12 @@ declare type PutServiceCombinedResult = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -8316,7 +8572,7 @@ declare type PutServiceCombinedResult = {
         /** Details about the current deployment status. */
         'deployment'?: {
             /** The current status of the deployment. Example: "COMPLETED" */
-            'status': 'IN_PROGRESS' | 'COMPLETED';
+            'status': 'PENDING' | 'IN_PROGRESS' | 'COMPLETED' | 'FAILED';
             /** The reason the current deployment was started. Example: "DEPLOYING" */
             'reason': 'SCALING' | 'DEPLOYING';
             /** The timestamp of when the deployment reached this status. Example: "2021-11-29T11:47:16.624Z" */
@@ -8370,6 +8626,10 @@ declare type PutServiceCombinedData = {
                 'storageSize'?: number;
             };
         };
+        'strategy'?: {
+            /** Configures the instance roll out strategy of your service. Currently only available via feature flag. */
+            'type'?: 'recreate' | 'rollout-steady' | 'rollout-balanced' | 'rollout-fast';
+        };
     };
     'ports'?: {
         /** The name used to identify the port. Example: "port-1" */
@@ -8419,12 +8679,12 @@ declare type PutServiceCombinedData = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -8441,6 +8701,12 @@ declare type PutServiceCombinedData = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -8527,6 +8793,10 @@ declare type PatchServiceCombinedResult = {
                 'storageSize'?: number;
             };
         };
+        'strategy'?: {
+            /** Configures the instance roll out strategy of your service. Currently only available via feature flag. */
+            'type'?: 'recreate' | 'rollout-steady' | 'rollout-balanced' | 'rollout-fast';
+        };
     };
     'ports'?: {
         /** The name used to identify the port. Example: "port-1" */
@@ -8576,12 +8846,12 @@ declare type PatchServiceCombinedResult = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -8598,6 +8868,12 @@ declare type PatchServiceCombinedResult = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -8661,7 +8937,7 @@ declare type PatchServiceCombinedResult = {
         /** Details about the current deployment status. */
         'deployment'?: {
             /** The current status of the deployment. Example: "COMPLETED" */
-            'status': 'IN_PROGRESS' | 'COMPLETED';
+            'status': 'PENDING' | 'IN_PROGRESS' | 'COMPLETED' | 'FAILED';
             /** The reason the current deployment was started. Example: "DEPLOYING" */
             'reason': 'SCALING' | 'DEPLOYING';
             /** The timestamp of when the deployment reached this status. Example: "2021-11-29T11:47:16.624Z" */
@@ -8706,6 +8982,10 @@ declare type PatchServiceCombinedData = {
                 'storageSize'?: number;
             };
         };
+        'strategy'?: {
+            /** Configures the instance roll out strategy of your service. Currently only available via feature flag. */
+            'type'?: 'recreate' | 'rollout-steady' | 'rollout-balanced' | 'rollout-fast';
+        };
     };
     'ports'?: {
         /** The name used to identify the port. Example: "port-1" */
@@ -8755,12 +9035,12 @@ declare type PatchServiceCombinedData = {
         'dockerfile'?: {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath'?: string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir'?: string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
         'buildpack'?: {
             /** Buildpack stack to use. Defaults to recommended stack `HEROKU_22_CLASSIC`. Example: "HEROKU_22_CLASSIC" */
@@ -8776,6 +9056,12 @@ declare type PatchServiceCombinedData = {
     'buildConfiguration'?: {
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
     };
     /** An object containing the runtime environment to set for the service. Keys may only contain letters, numbers, hyphens, forward slashes and dots. Example: {"VARIABLE_1":"abcdef","VARIABLE_2":"12345"} */
     'runtimeEnvironment'?: any;
@@ -8851,7 +9137,7 @@ declare type CreateServiceDeploymentResult = {
         /** Details about the current deployment status. */
         'deployment'?: {
             /** The current status of the deployment. Example: "COMPLETED" */
-            'status': 'IN_PROGRESS' | 'COMPLETED';
+            'status': 'PENDING' | 'IN_PROGRESS' | 'COMPLETED' | 'FAILED';
             /** The reason the current deployment was started. Example: "DEPLOYING" */
             'reason': 'SCALING' | 'DEPLOYING';
             /** The timestamp of when the deployment reached this status. Example: "2021-11-29T11:47:16.624Z" */
@@ -8967,6 +9253,10 @@ declare type CreateServiceDeploymentData = {
                 'storageSize'?: number;
             };
         };
+        'strategy'?: {
+            /** Configures the instance roll out strategy of your service. Currently only available via feature flag. */
+            'type'?: 'recreate' | 'rollout-steady' | 'rollout-balanced' | 'rollout-fast';
+        };
         'internal': {
             /** ID of the build service to deploy Example: "example-build-service" */
             'id'?: string;
@@ -9006,6 +9296,10 @@ declare type CreateServiceDeploymentData = {
                 'storageSize'?: number;
             };
         };
+        'strategy'?: {
+            /** Configures the instance roll out strategy of your service. Currently only available via feature flag. */
+            'type'?: 'recreate' | 'rollout-steady' | 'rollout-balanced' | 'rollout-fast';
+        };
         'external': {
             /** Image to be deployed. When not deploying from Dockerhub the URL must be specified. Example: "nginx:latest" */
             'imagePath': string;
@@ -9041,6 +9335,10 @@ declare type CreateServiceDeploymentData = {
                 'storageSize'?: number;
             };
         };
+        'strategy'?: {
+            /** Configures the instance roll out strategy of your service. Currently only available via feature flag. */
+            'type'?: 'recreate' | 'rollout-steady' | 'rollout-balanced' | 'rollout-fast';
+        };
     };
     'ports'?: {
         /** The name used to identify the port. Example: "port-1" */
@@ -9149,6 +9447,10 @@ declare type PutServiceDeploymentResult = {
                 'storageSize'?: number;
             };
         };
+        'strategy'?: {
+            /** Configures the instance roll out strategy of your service. Currently only available via feature flag. */
+            'type'?: 'recreate' | 'rollout-steady' | 'rollout-balanced' | 'rollout-fast';
+        };
         'internal'?: {
             /** ID of the build service to deploy Example: "example-build-service" */
             'id'?: string;
@@ -9243,7 +9545,7 @@ declare type PutServiceDeploymentResult = {
         /** Details about the current deployment status. */
         'deployment'?: {
             /** The current status of the deployment. Example: "COMPLETED" */
-            'status': 'IN_PROGRESS' | 'COMPLETED';
+            'status': 'PENDING' | 'IN_PROGRESS' | 'COMPLETED' | 'FAILED';
             /** The reason the current deployment was started. Example: "DEPLOYING" */
             'reason': 'SCALING' | 'DEPLOYING';
             /** The timestamp of when the deployment reached this status. Example: "2021-11-29T11:47:16.624Z" */
@@ -9298,6 +9600,10 @@ declare type PutServiceDeploymentData = {
                 'storageSize'?: number;
             };
         };
+        'strategy'?: {
+            /** Configures the instance roll out strategy of your service. Currently only available via feature flag. */
+            'type'?: 'recreate' | 'rollout-steady' | 'rollout-balanced' | 'rollout-fast';
+        };
         'internal': {
             /** ID of the build service to deploy Example: "example-build-service" */
             'id'?: string;
@@ -9337,6 +9643,10 @@ declare type PutServiceDeploymentData = {
                 'storageSize'?: number;
             };
         };
+        'strategy'?: {
+            /** Configures the instance roll out strategy of your service. Currently only available via feature flag. */
+            'type'?: 'recreate' | 'rollout-steady' | 'rollout-balanced' | 'rollout-fast';
+        };
         'external': {
             /** Image to be deployed. When not deploying from Dockerhub the URL must be specified. Example: "nginx:latest" */
             'imagePath': string;
@@ -9372,6 +9682,10 @@ declare type PutServiceDeploymentData = {
                 'storageSize'?: number;
             };
         };
+        'strategy'?: {
+            /** Configures the instance roll out strategy of your service. Currently only available via feature flag. */
+            'type'?: 'recreate' | 'rollout-steady' | 'rollout-balanced' | 'rollout-fast';
+        };
     };
     'ports'?: {
         /** The name used to identify the port. Example: "port-1" */
@@ -9480,6 +9794,10 @@ declare type PatchServiceDeploymentResult = {
                 'storageSize'?: number;
             };
         };
+        'strategy'?: {
+            /** Configures the instance roll out strategy of your service. Currently only available via feature flag. */
+            'type'?: 'recreate' | 'rollout-steady' | 'rollout-balanced' | 'rollout-fast';
+        };
         'internal'?: {
             /** ID of the build service to deploy Example: "example-build-service" */
             'id'?: string;
@@ -9574,7 +9892,7 @@ declare type PatchServiceDeploymentResult = {
         /** Details about the current deployment status. */
         'deployment'?: {
             /** The current status of the deployment. Example: "COMPLETED" */
-            'status': 'IN_PROGRESS' | 'COMPLETED';
+            'status': 'PENDING' | 'IN_PROGRESS' | 'COMPLETED' | 'FAILED';
             /** The reason the current deployment was started. Example: "DEPLOYING" */
             'reason': 'SCALING' | 'DEPLOYING';
             /** The timestamp of when the deployment reached this status. Example: "2021-11-29T11:47:16.624Z" */
@@ -9701,7 +10019,7 @@ declare type CreateServiceBuildResult = {
         /** Details about the current deployment status. */
         'deployment'?: {
             /** The current status of the deployment. Example: "COMPLETED" */
-            'status': 'IN_PROGRESS' | 'COMPLETED';
+            'status': 'PENDING' | 'IN_PROGRESS' | 'COMPLETED' | 'FAILED';
             /** The reason the current deployment was started. Example: "DEPLOYING" */
             'reason': 'SCALING' | 'DEPLOYING';
             /** The timestamp of when the deployment reached this status. Example: "2021-11-29T11:47:16.624Z" */
@@ -9788,12 +10106,12 @@ declare type CreateServiceBuildData = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -9814,6 +10132,12 @@ declare type CreateServiceBuildData = {
         'branchRestrictions'?: string[];
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -9858,12 +10182,12 @@ declare type PutServiceBuildResult = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -9884,6 +10208,12 @@ declare type PutServiceBuildResult = {
         'branchRestrictions'?: string[];
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -9947,12 +10277,12 @@ declare type PutServiceBuildData = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -9973,6 +10303,12 @@ declare type PutServiceBuildData = {
         'branchRestrictions'?: string[];
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -10017,12 +10353,12 @@ declare type PatchServiceBuildResult = {
         'dockerfile': {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath': string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir': string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
     } | {
         'buildpack': {
@@ -10043,6 +10379,12 @@ declare type PatchServiceBuildResult = {
         'branchRestrictions'?: string[];
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
         /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
         'dockerfileTarget'?: string;
         /** Include .git folder inside the build context */
@@ -10106,12 +10448,12 @@ declare type PatchServiceBuildData = {
         'dockerfile'?: {
             /** Build engine to use. Defaults to recommended build engine `kaniko` Example: "kaniko" */
             'buildEngine'?: 'kaniko' | 'buildkit';
-            /** Should intermediate image layers be cached? */
-            'useCache'?: boolean;
             /** The file path of the Dockerfile. Example: "/Dockerfile" */
             'dockerFilePath'?: string;
             /** The working directory of the Dockerfile. Example: "/" */
             'dockerWorkDir'?: string;
+            /** Should intermediate image layers be cached? */
+            'useCache'?: boolean;
         };
         'buildpack'?: {
             /** Buildpack stack to use. Defaults to recommended stack `HEROKU_22_CLASSIC`. Example: "HEROKU_22_CLASSIC" */
@@ -10131,6 +10473,12 @@ declare type PatchServiceBuildData = {
         'branchRestrictions'?: string[];
         /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
         'pathIgnoreRules'?: string[];
+        /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+        'isAllowList'?: boolean;
+        /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+        'ciIgnoreFlagsEnabled'?: boolean;
+        /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+        'ciIgnoreFlags'?: string[];
     };
     /** An object containing the build arguments to set for the service Example: {"ARGUMENT_1":"abcdef","ARGUMENT_2":"12345"} */
     'buildArguments'?: any;
@@ -10181,7 +10529,7 @@ declare type GetServiceResult = {
         /** Details about the current deployment status. */
         'deployment'?: {
             /** The current status of the deployment. Example: "COMPLETED" */
-            'status': 'IN_PROGRESS' | 'COMPLETED';
+            'status': 'PENDING' | 'IN_PROGRESS' | 'COMPLETED' | 'FAILED';
             /** The reason the current deployment was started. Example: "DEPLOYING" */
             'reason': 'SCALING' | 'DEPLOYING';
             /** The timestamp of when the deployment reached this status. Example: "2021-11-29T11:47:16.624Z" */
@@ -10832,6 +11180,12 @@ declare type UpdateServiceBuildoptionsData = {
     'branchRestrictions'?: string[];
     /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
     'pathIgnoreRules'?: string[];
+    /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+    'isAllowList'?: boolean;
+    /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+    'ciIgnoreFlagsEnabled'?: boolean;
+    /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+    'ciIgnoreFlags'?: string[];
     /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
     'dockerfileTarget'?: string;
     /** Include .git folder inside the build context */
@@ -10851,6 +11205,12 @@ declare type UpdateServiceBuildoptionsData = {
     };
     /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
     'pathIgnoreRules'?: string[];
+    /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+    'isAllowList'?: boolean;
+    /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+    'ciIgnoreFlagsEnabled'?: boolean;
+    /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+    'ciIgnoreFlags'?: string[];
 } | {
     /** An array of pull request build rules. Only supported for build services. Each commit belonging to a pull request on a branch that matches one of the provided build rules will be built automatically. */
     'prRestrictions'?: string[];
@@ -10858,6 +11218,12 @@ declare type UpdateServiceBuildoptionsData = {
     'branchRestrictions'?: string[];
     /** An array of path ignore rules. A commit will only be built if a file has been changed that does not match any of the ignore rules. Path ignore rules follow `.gitignore` syntax. */
     'pathIgnoreRules'?: string[];
+    /** If `true`, the functionality of `pathIgnoreRules` will be inverted. A commit will only be built if a file has been changed that matches one or more of the rules in `pathIgnoreRules`. */
+    'isAllowList'?: boolean;
+    /** If `true`, enables commit ignore flags. If a commit message contains one or more of the flags in `ciIgnoreFlags`, that commit will not be built. */
+    'ciIgnoreFlagsEnabled'?: boolean;
+    /** An array of commit ignore flags. If a commit message contains one or more of these flags, that commit will not be built. Defaults to `[, "[skip ci]", "[ci skip]", "[no ci]", "[skip nf]", "[nf skip]", "[northflank skip]", "[skip northflank]"]` Example: ["[skip ci]","[ci skip]","[no ci]","[skip nf]","[nf skip]","[northflank skip]","[skip northflank]"] */
+    'ciIgnoreFlags'?: string[];
     /** If your Dockerfile contains multiple build stages, you can specify the target stage by entering its name here. */
     'dockerfileTarget'?: string;
     /** Include .git folder inside the build context */
@@ -11307,23 +11673,18 @@ declare class GetServicePullrequestsEndpoint extends GetApiEndpoint<GetServicePu
 declare type ListTemplatesResult = {
     /** An array of template objects. */
     'templates': {
-        /** ID of the template. Example: "example-template" */
+        /** Name of the template. Example: "Example Template" */
+        'name': string;
+        /** Description of the template. Example: "This is a sample template." */
+        'description'?: string;
+        /** The version of the Northflank API to run the template against. Example: "v1" */
+        'apiVersion': 'v1';
+        /** Identifier for the template Example: "example-template" */
         'id': string;
-        /** Timestamp of when the template was created. Example: "2022-06-14 15:10:42.842Z" */
-        'createdAt': string;
-        /** Timestamp of when the template was last updated. Example: "2022-06-14 15:10:42.842Z" */
-        'updatedAt': string;
-        /** If true, this template runs automatically after any changes are applied. */
-        'autorun': boolean;
-        /** Details about the template. */
-        'content': {
-            /** Name of the template. Example: "Example Template" */
-            'name': string;
-            /** Description of the template. Example: "This is a sample template." */
-            'description'?: string;
-            /** The version of the Northflank API to run the template against. Example: "v1" */
-            'apiVersion': 'v1';
-        };
+        /** time of creation */
+        'createdAt'?: string;
+        /** time of update */
+        'updatedAt'?: string;
     }[];
 };
 declare type ListTemplatesCall = (opts: ListTemplatesRequest) => Promise<ApiCallResponse<ListTemplatesResult>>;
@@ -11350,123 +11711,113 @@ declare class ListTemplatesEndpoint extends GetApiEndpoint<ListTemplatesRequest,
 declare type CreateTemplateResult = {
     /** Details about the newly created template. */
     'template': {
-        /** ID of the template. Example: "example-template" */
+        /** Name of the template. Example: "Example Template" */
+        'name': string;
+        /** Description of the template. Example: "This is a sample template." */
+        'description'?: string;
+        /** The version of the Northflank API to run the template against. Example: "v1" */
+        'apiVersion': 'v1';
+        /** Details of the project the template will run in. */
+        'project': {
+            /** The ID of the project to use. */
+            'id': string;
+        } | {
+            'spec': {
+                /** The name of the project. Example: "New Project" */
+                'name': string;
+                /** The description of the project. Example: "This is a new project." */
+                'description'?: string;
+                /** The color of the project in the Northflank App. Example: "#EF233C" */
+                'color'?: string;
+                /** The region the project will be hosted in. Example: "europe-west" */
+                'region': string;
+            } | {
+                /** The name of the project. Example: "New Project" */
+                'name': string;
+                /** The description of the project. Example: "This is a new project." */
+                'description'?: string;
+                /** The color of the project in the Northflank App. Example: "#EF233C" */
+                'color'?: string;
+                /** The BYOC cluster this project will be hosted in. Example: "gcp-cluster-1" */
+                'clusterId'?: string;
+            };
+        };
+        /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
+        'arguments'?: any;
+        'spec': any;
+        /** Identifier for the template Example: "example-template" */
         'id': string;
-        /** Timestamp of when the template was created. Example: "2022-06-14 15:10:42.842Z" */
-        'createdAt': string;
-        /** Timestamp of when the template was last updated. Example: "2022-06-14 15:10:42.842Z" */
-        'updatedAt': string;
-        /** If true, this template runs automatically after any changes are applied. */
-        'autorun': boolean;
-        /** Details about the GitOps settings for the template. */
-        'vcsData'?: {
-            /** URL of the Git repo the template is being synced with. Example: "https://github.com/northflank-examples/remix-postgres-redis-demo" */
-            'repoUrl': string;
-            /** The VCS provider for the template. Example: "github" */
+        'gitops'?: {
+            /** The VCS provider to use. Example: "github" */
             'vcsService': 'bitbucket' | 'gitlab' | 'github' | 'self-hosted';
-            /** If projectType is self-hosted, the ID of the self-hosted vcs being used. */
+            /** If projectType is self-hosted, the ID of the self-hosted vcs to use. */
             'selfHostedVcsId'?: string;
-            /** The name of the branch. Example: "main" */
+            /** By default, if you have multiple version control accounts of the same provider linked, Northflank will pick a linked account that has access to the repository. If `accountLogin` is provided, Northflank will instead use your linked account with that login name. Example: "github-user" */
+            'accountLogin'?: string;
+            /** URL of the Git repo to sync the template with. Example: "https://github.com/northflank-examples/remix-postgres-redis-demo" */
+            'repoUrl': string;
+            /** The name of the branch to use. Example: "main" */
             'branch': string;
-            /** The file path to the template in the repository. Example: "northflank.json" */
+            /** The file path to the template in the repository. If using an existing template, it should be in JSON format. Example: "northflank.json" */
             'filePath': string;
             /** The SHA of the current commit that is being used for the template. Example: "8c7e040ee3737ddc3a713363ae72bbe960e9fb16" */
             'templateSha': string;
         };
-        /** The content of the template. */
-        'content'?: {
-            /** Name of the template. Example: "Example Template" */
-            'name': string;
-            /** Description of the template. Example: "This is a sample template." */
-            'description'?: string;
-            /** The version of the Northflank API to run the template against. Example: "v1" */
-            'apiVersion': 'v1';
-            /** Details of the project the template will run in. */
-            'project': {
-                /** The ID of the project to use. */
-                'id': string;
-            } | {
-                'spec': {
-                    /** The name of the project. Example: "New Project" */
-                    'name': string;
-                    /** The description of the project. Example: "This is a new project." */
-                    'description'?: string;
-                    /** The color of the project in the Northflank App. Example: "#EF233C" */
-                    'color'?: string;
-                    /** The region the project will be hosted in. Example: "europe-west" */
-                    'region': string;
-                } | {
-                    /** The name of the project. Example: "New Project" */
-                    'name': string;
-                    /** The description of the project. Example: "This is a new project." */
-                    'description'?: string;
-                    /** The color of the project in the Northflank App. Example: "#EF233C" */
-                    'color'?: string;
-                    /** The BYOC cluster this project will be hosted in. Example: "gcp-cluster-1" */
-                    'clusterId'?: string;
-                };
-            };
-            /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
-            'arguments'?: any;
-            'refs'?: any;
-            'spec': any;
+        'options': {
+            /** Whether autorun is enabled */
+            'autorun': boolean;
         };
+        /** time of creation */
+        'createdAt'?: string;
+        /** time of update */
+        'updatedAt'?: string;
     };
-    /** Details about the newly created template run. */
     'templateRun'?: {
-        /** ID of the template run. Example: "501c1e03-a021-4659-9048-85f8f6ee2bc7" */
-        'id': string;
-        /** Timestamp of when the run was initiated. Example: "2022-06-14 15:10:42.842Z" */
-        'createdAt': string;
-        /** Timestamp of when the run was last updated. Example: "2022-06-14 15:10:42.842Z" */
-        'updatedAt': string;
-        /** Details about the template being run. */
-        'template': {
-            /** ID of the template Example: "example-template" */
-            'id': string;
-            /** The name of the template Example: "Example Template" */
-            'name': string;
-        };
-        /** Status of the template run. Example: "success" */
-        'status': 'waiting' | 'failure' | 'retrying' | 'success' | 'unknown';
-        /** Details about the template run. */
-        'content': {
-            /** Name of the template. Example: "Example Template" */
-            'name': string;
-            /** Description of the template. Example: "This is a sample template." */
-            'description'?: string;
-            /** The version of the Northflank API to run the template against. Example: "v1" */
-            'apiVersion': 'v1';
-            /** Details of the project the template will run in. */
-            'project': {
-                /** The ID of the project to use. */
-                'id': string;
-            } | {
-                'spec': {
-                    /** The name of the project. Example: "New Project" */
-                    'name': string;
-                    /** The description of the project. Example: "This is a new project." */
-                    'description'?: string;
-                    /** The color of the project in the Northflank App. Example: "#EF233C" */
-                    'color'?: string;
-                    /** The region the project will be hosted in. Example: "europe-west" */
-                    'region': string;
-                } | {
-                    /** The name of the project. Example: "New Project" */
-                    'name': string;
-                    /** The description of the project. Example: "This is a new project." */
-                    'description'?: string;
-                    /** The color of the project in the Northflank App. Example: "#EF233C" */
-                    'color'?: string;
-                    /** The BYOC cluster this project will be hosted in. Example: "gcp-cluster-1" */
-                    'clusterId'?: string;
-                };
+        /** Name of the template. Example: "Example Template" */
+        'name': string;
+        /** Description of the template. Example: "This is a sample template." */
+        'description'?: string;
+        /** The version of the Northflank API to run the template against. Example: "v1" */
+        'apiVersion': 'v1';
+        /** Details of the project the template will run in. */
+        'project': {
+            /** The ID of the project to use. */
+            'id': string;
+        } | {
+            'spec': {
+                /** The name of the project. Example: "New Project" */
+                'name': string;
+                /** The description of the project. Example: "This is a new project." */
+                'description'?: string;
+                /** The color of the project in the Northflank App. Example: "#EF233C" */
+                'color'?: string;
+                /** The region the project will be hosted in. Example: "europe-west" */
+                'region': string;
+            } | {
+                /** The name of the project. Example: "New Project" */
+                'name': string;
+                /** The description of the project. Example: "This is a new project." */
+                'description'?: string;
+                /** The color of the project in the Northflank App. Example: "#EF233C" */
+                'color'?: string;
+                /** The BYOC cluster this project will be hosted in. Example: "gcp-cluster-1" */
+                'clusterId'?: string;
             };
-            /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
-            'arguments'?: any;
-            'refs'?: any;
-            'spec': any;
         };
+        /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
+        'arguments'?: any;
+        'spec': any;
+        'refs'?: any;
+        /** Identifier for the template run Example: "3dd592f6-ce63-45ee-acf8-13dc5ec5235c" */
+        'id': string;
+        /** Identifier for the template Example: "example-template" */
+        'templateId': string;
+        /** Status of the template run Example: "pending" */
+        'status': 'pending' | 'running' | 'success' | 'failure';
+        /** time of creation */
+        'createdAt'?: string;
+        /** time of update */
+        'updatedAt'?: string;
     };
 };
 declare type CreateTemplateCall = (opts: CreateTemplateRequest) => Promise<ApiCallResponse<CreateTemplateResult>>;
@@ -11507,7 +11858,6 @@ declare type CreateTemplateData = {
     };
     /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
     'arguments'?: any;
-    'refs'?: any;
     'spec': any;
     /** Argument overrides stored outside of the template. If GitOps is enabled, these will not be saved in version control. */
     'argumentOverrides'?: any;
@@ -11554,7 +11904,6 @@ declare type CreateTemplateData = {
     };
     /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
     'arguments'?: any;
-    'refs'?: any;
     'spec': any;
     /** Argument overrides stored outside of the template. If GitOps is enabled, these will not be saved in version control. */
     'argumentOverrides'?: any;
@@ -11569,14 +11918,14 @@ declare type CreateTemplateData = {
     };
     /** GitOps data for syncing this template with a file in version control. */
     'gitops': {
-        /** URL of the Git repo to sync the template with. Example: "https://github.com/northflank-examples/remix-postgres-redis-demo" */
-        'repoUrl': string;
         /** The VCS provider to use. Example: "github" */
         'vcsService': 'bitbucket' | 'gitlab' | 'github' | 'self-hosted';
         /** If projectType is self-hosted, the ID of the self-hosted vcs to use. */
         'selfHostedVcsId'?: string;
         /** By default, if you have multiple version control accounts of the same provider linked, Northflank will pick a linked account that has access to the repository. If `accountLogin` is provided, Northflank will instead use your linked account with that login name. Example: "github-user" */
         'accountLogin'?: string;
+        /** URL of the Git repo to sync the template with. Example: "https://github.com/northflank-examples/remix-postgres-redis-demo" */
+        'repoUrl': string;
         /** The name of the branch to use. Example: "main" */
         'branch': string;
         /** The file path to the template in the repository. If using an existing template, it should be in JSON format. Example: "northflank.json" */
@@ -11587,9 +11936,6 @@ declare type CreateTemplateData = {
     'name': string;
     /** Description of the template. Example: "This is a sample template." */
     'description'?: string;
-    /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
-    'arguments'?: any;
-    'refs'?: any;
     /** Argument overrides stored outside of the template. If GitOps is enabled, these will not be saved in version control. */
     'argumentOverrides'?: any;
     /** Additional options for the template creation. */
@@ -11603,14 +11949,14 @@ declare type CreateTemplateData = {
     };
     /** GitOps data for syncing this template with a file in version control. */
     'gitops': {
-        /** URL of the Git repo to sync the template with. Example: "https://github.com/northflank-examples/remix-postgres-redis-demo" */
-        'repoUrl': string;
         /** The VCS provider to use. Example: "github" */
         'vcsService': 'bitbucket' | 'gitlab' | 'github' | 'self-hosted';
         /** If projectType is self-hosted, the ID of the self-hosted vcs to use. */
         'selfHostedVcsId'?: string;
         /** By default, if you have multiple version control accounts of the same provider linked, Northflank will pick a linked account that has access to the repository. If `accountLogin` is provided, Northflank will instead use your linked account with that login name. Example: "github-user" */
         'accountLogin'?: string;
+        /** URL of the Git repo to sync the template with. Example: "https://github.com/northflank-examples/remix-postgres-redis-demo" */
+        'repoUrl': string;
         /** The name of the branch to use. Example: "main" */
         'branch': string;
         /** The file path to the template in the repository. If using an existing template, it should be in JSON format. Example: "northflank.json" */
@@ -11627,31 +11973,95 @@ declare class CreateTemplateEndpoint extends PostApiEndpoint<CreateTemplateReque
 }
 
 declare type GetTemplateResult = {
-    /** ID of the template. Example: "example-template" */
+    /** Name of the template. Example: "Example Template" */
+    'name': string;
+    /** Description of the template. Example: "This is a sample template." */
+    'description'?: string;
+    /** The version of the Northflank API to run the template against. Example: "v1" */
+    'apiVersion': 'v1';
+    /** Details of the project the template will run in. */
+    'project': {
+        /** The ID of the project to use. */
+        'id': string;
+    } | {
+        'spec': {
+            /** The name of the project. Example: "New Project" */
+            'name': string;
+            /** The description of the project. Example: "This is a new project." */
+            'description'?: string;
+            /** The color of the project in the Northflank App. Example: "#EF233C" */
+            'color'?: string;
+            /** The region the project will be hosted in. Example: "europe-west" */
+            'region': string;
+        } | {
+            /** The name of the project. Example: "New Project" */
+            'name': string;
+            /** The description of the project. Example: "This is a new project." */
+            'description'?: string;
+            /** The color of the project in the Northflank App. Example: "#EF233C" */
+            'color'?: string;
+            /** The BYOC cluster this project will be hosted in. Example: "gcp-cluster-1" */
+            'clusterId'?: string;
+        };
+    };
+    /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
+    'arguments'?: any;
+    'spec': any;
+    /** Identifier for the template Example: "example-template" */
     'id': string;
-    /** Timestamp of when the template was created. Example: "2022-06-14 15:10:42.842Z" */
-    'createdAt': string;
-    /** Timestamp of when the template was last updated. Example: "2022-06-14 15:10:42.842Z" */
-    'updatedAt': string;
-    /** If true, this template runs automatically after any changes are applied. */
-    'autorun': boolean;
-    /** Details about the GitOps settings for the template. */
-    'vcsData'?: {
-        /** URL of the Git repo the template is being synced with. Example: "https://github.com/northflank-examples/remix-postgres-redis-demo" */
-        'repoUrl': string;
-        /** The VCS provider for the template. Example: "github" */
+    'gitops'?: {
+        /** The VCS provider to use. Example: "github" */
         'vcsService': 'bitbucket' | 'gitlab' | 'github' | 'self-hosted';
-        /** If projectType is self-hosted, the ID of the self-hosted vcs being used. */
+        /** If projectType is self-hosted, the ID of the self-hosted vcs to use. */
         'selfHostedVcsId'?: string;
-        /** The name of the branch. Example: "main" */
+        /** By default, if you have multiple version control accounts of the same provider linked, Northflank will pick a linked account that has access to the repository. If `accountLogin` is provided, Northflank will instead use your linked account with that login name. Example: "github-user" */
+        'accountLogin'?: string;
+        /** URL of the Git repo to sync the template with. Example: "https://github.com/northflank-examples/remix-postgres-redis-demo" */
+        'repoUrl': string;
+        /** The name of the branch to use. Example: "main" */
         'branch': string;
-        /** The file path to the template in the repository. Example: "northflank.json" */
+        /** The file path to the template in the repository. If using an existing template, it should be in JSON format. Example: "northflank.json" */
         'filePath': string;
         /** The SHA of the current commit that is being used for the template. Example: "8c7e040ee3737ddc3a713363ae72bbe960e9fb16" */
         'templateSha': string;
     };
-    /** The content of the template. */
-    'content'?: {
+    'options': {
+        /** Whether autorun is enabled */
+        'autorun': boolean;
+    };
+    /** time of creation */
+    'createdAt'?: string;
+    /** time of update */
+    'updatedAt'?: string;
+};
+declare type GetTemplateCall = (opts: GetTemplateRequest) => Promise<ApiCallResponse<GetTemplateResult>>;
+declare type GetTemplateRequest = {
+    parameters: GetTemplateParameters;
+    options?: GetTemplateOptions;
+};
+declare type GetTemplateParameters = {
+    /** ID of the template */ 'templateId': string;
+};
+declare type GetTemplateOptions = {
+    /** The number of results to display per request. Maximum of 100 results per page. */
+    'per_page'?: number;
+    /** The page number to access. */
+    'page'?: number;
+    /** The cursor returned from the previous page of results, used to request the next page. */
+    'cursor'?: string;
+};
+/** Get information about the given template. */
+declare class GetTemplateEndpoint extends GetApiEndpoint<GetTemplateRequest, GetTemplateResult> {
+    description: string;
+    withAuth: boolean;
+    requiredPermissions: string;
+    endpointUrl: (opts: GetTemplateRequest) => string;
+    body: () => undefined;
+}
+
+declare type UpdateTemplateResult = {
+    /** Details about the updated template. */
+    'template': {
         /** Name of the template. Example: "Example Template" */
         'name': string;
         /** Description of the template. Example: "This is a sample template." */
@@ -11685,61 +12095,35 @@ declare type GetTemplateResult = {
         };
         /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
         'arguments'?: any;
-        'refs'?: any;
         'spec': any;
+        /** Identifier for the template Example: "example-template" */
+        'id': string;
+        'gitops'?: {
+            /** The VCS provider to use. Example: "github" */
+            'vcsService': 'bitbucket' | 'gitlab' | 'github' | 'self-hosted';
+            /** If projectType is self-hosted, the ID of the self-hosted vcs to use. */
+            'selfHostedVcsId'?: string;
+            /** By default, if you have multiple version control accounts of the same provider linked, Northflank will pick a linked account that has access to the repository. If `accountLogin` is provided, Northflank will instead use your linked account with that login name. Example: "github-user" */
+            'accountLogin'?: string;
+            /** URL of the Git repo to sync the template with. Example: "https://github.com/northflank-examples/remix-postgres-redis-demo" */
+            'repoUrl': string;
+            /** The name of the branch to use. Example: "main" */
+            'branch': string;
+            /** The file path to the template in the repository. If using an existing template, it should be in JSON format. Example: "northflank.json" */
+            'filePath': string;
+            /** The SHA of the current commit that is being used for the template. Example: "8c7e040ee3737ddc3a713363ae72bbe960e9fb16" */
+            'templateSha': string;
+        };
+        'options': {
+            /** Whether autorun is enabled */
+            'autorun': boolean;
+        };
+        /** time of creation */
+        'createdAt'?: string;
+        /** time of update */
+        'updatedAt'?: string;
     };
-};
-declare type GetTemplateCall = (opts: GetTemplateRequest) => Promise<ApiCallResponse<GetTemplateResult>>;
-declare type GetTemplateRequest = {
-    parameters: GetTemplateParameters;
-    options?: GetTemplateOptions;
-};
-declare type GetTemplateParameters = {
-    /** ID of the template */ 'templateId': string;
-};
-declare type GetTemplateOptions = {
-    /** The number of results to display per request. Maximum of 100 results per page. */
-    'per_page'?: number;
-    /** The page number to access. */
-    'page'?: number;
-    /** The cursor returned from the previous page of results, used to request the next page. */
-    'cursor'?: string;
-};
-/** Get information about the given template. */
-declare class GetTemplateEndpoint extends GetApiEndpoint<GetTemplateRequest, GetTemplateResult> {
-    description: string;
-    withAuth: boolean;
-    requiredPermissions: string;
-    endpointUrl: (opts: GetTemplateRequest) => string;
-    body: () => undefined;
-}
-
-declare type UpdateTemplateResult = {
-    /** ID of the template. Example: "example-template" */
-    'id': string;
-    /** Timestamp of when the template was created. Example: "2022-06-14 15:10:42.842Z" */
-    'createdAt': string;
-    /** Timestamp of when the template was last updated. Example: "2022-06-14 15:10:42.842Z" */
-    'updatedAt': string;
-    /** If true, this template runs automatically after any changes are applied. */
-    'autorun': boolean;
-    /** Details about the GitOps settings for the template. */
-    'vcsData'?: {
-        /** URL of the Git repo the template is being synced with. Example: "https://github.com/northflank-examples/remix-postgres-redis-demo" */
-        'repoUrl': string;
-        /** The VCS provider for the template. Example: "github" */
-        'vcsService': 'bitbucket' | 'gitlab' | 'github' | 'self-hosted';
-        /** If projectType is self-hosted, the ID of the self-hosted vcs being used. */
-        'selfHostedVcsId'?: string;
-        /** The name of the branch. Example: "main" */
-        'branch': string;
-        /** The file path to the template in the repository. Example: "northflank.json" */
-        'filePath': string;
-        /** The SHA of the current commit that is being used for the template. Example: "8c7e040ee3737ddc3a713363ae72bbe960e9fb16" */
-        'templateSha': string;
-    };
-    /** The content of the template. */
-    'content'?: {
+    'templateRun'?: {
         /** Name of the template. Example: "Example Template" */
         'name': string;
         /** Description of the template. Example: "This is a sample template." */
@@ -11773,8 +12157,18 @@ declare type UpdateTemplateResult = {
         };
         /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
         'arguments'?: any;
-        'refs'?: any;
         'spec': any;
+        'refs'?: any;
+        /** Identifier for the template run Example: "3dd592f6-ce63-45ee-acf8-13dc5ec5235c" */
+        'id': string;
+        /** Identifier for the template Example: "example-template" */
+        'templateId': string;
+        /** Status of the template run Example: "pending" */
+        'status': 'pending' | 'running' | 'success' | 'failure';
+        /** time of creation */
+        'createdAt'?: string;
+        /** time of update */
+        'updatedAt'?: string;
     };
 };
 declare type UpdateTemplateCall = (opts: UpdateTemplateRequest) => Promise<ApiCallResponse<UpdateTemplateResult>>;
@@ -11819,7 +12213,6 @@ declare type UpdateTemplateData = {
     };
     /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
     'arguments'?: any;
-    'refs'?: any;
     'spec': any;
     /** Argument overrides stored outside of the template. If GitOps is enabled, these will not be saved in version control. */
     'argumentOverrides'?: any;
@@ -11862,7 +12255,6 @@ declare type UpdateTemplateData = {
     };
     /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
     'arguments'?: any;
-    'refs'?: any;
     'spec': any;
     /** Argument overrides stored outside of the template. If GitOps is enabled, these will not be saved in version control. */
     'argumentOverrides'?: any;
@@ -11873,14 +12265,14 @@ declare type UpdateTemplateData = {
     };
     /** GitOps data for syncing this template with a file in version control. If set to `null`, removes GitOps handling from this template. */
     'gitops': {
-        /** URL of the Git repo to sync the template with. Example: "https://github.com/northflank-examples/remix-postgres-redis-demo" */
-        'repoUrl': string;
         /** The VCS provider to use. Example: "github" */
         'vcsService': 'bitbucket' | 'gitlab' | 'github' | 'self-hosted';
         /** If projectType is self-hosted, the ID of the self-hosted vcs to use. */
         'selfHostedVcsId'?: string;
         /** By default, if you have multiple version control accounts of the same provider linked, Northflank will pick a linked account that has access to the repository. If `accountLogin` is provided, Northflank will instead use your linked account with that login name. Example: "github-user" */
         'accountLogin'?: string;
+        /** URL of the Git repo to sync the template with. Example: "https://github.com/northflank-examples/remix-postgres-redis-demo" */
+        'repoUrl': string;
         /** The name of the branch to use. Example: "main" */
         'branch': string;
         /** The file path to the template in the repository. If using an existing template, it should be in JSON format. Example: "northflank.json" */
@@ -11891,9 +12283,6 @@ declare type UpdateTemplateData = {
     'name': string;
     /** Description of the template. Example: "This is a sample template." */
     'description'?: string;
-    /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
-    'arguments'?: any;
-    'refs'?: any;
     /** Argument overrides stored outside of the template. If GitOps is enabled, these will not be saved in version control. */
     'argumentOverrides'?: any;
     /** Additional options for the template creation. */
@@ -11903,14 +12292,14 @@ declare type UpdateTemplateData = {
     };
     /** GitOps data for syncing this template with a file in version control. If set to `null`, removes GitOps handling from this template. */
     'gitops': {
-        /** URL of the Git repo to sync the template with. Example: "https://github.com/northflank-examples/remix-postgres-redis-demo" */
-        'repoUrl': string;
         /** The VCS provider to use. Example: "github" */
         'vcsService': 'bitbucket' | 'gitlab' | 'github' | 'self-hosted';
         /** If projectType is self-hosted, the ID of the self-hosted vcs to use. */
         'selfHostedVcsId'?: string;
         /** By default, if you have multiple version control accounts of the same provider linked, Northflank will pick a linked account that has access to the repository. If `accountLogin` is provided, Northflank will instead use your linked account with that login name. Example: "github-user" */
         'accountLogin'?: string;
+        /** URL of the Git repo to sync the template with. Example: "https://github.com/northflank-examples/remix-postgres-redis-demo" */
+        'repoUrl': string;
         /** The name of the branch to use. Example: "main" */
         'branch': string;
         /** The file path to the template in the repository. If using an existing template, it should be in JSON format. Example: "northflank.json" */
@@ -11944,59 +12333,51 @@ declare class DeleteTemplateEndpoint extends DeleteApiEndpoint<DeleteTemplateReq
 }
 
 declare type RunTemplateResult = {
-    /** ID of the template run. Example: "501c1e03-a021-4659-9048-85f8f6ee2bc7" */
-    'id': string;
-    /** Timestamp of when the run was initiated. Example: "2022-06-14 15:10:42.842Z" */
-    'createdAt': string;
-    /** Timestamp of when the run was last updated. Example: "2022-06-14 15:10:42.842Z" */
-    'updatedAt': string;
-    /** Details about the template being run. */
-    'template': {
-        /** ID of the template Example: "example-template" */
+    /** Name of the template. Example: "Example Template" */
+    'name': string;
+    /** Description of the template. Example: "This is a sample template." */
+    'description'?: string;
+    /** The version of the Northflank API to run the template against. Example: "v1" */
+    'apiVersion': 'v1';
+    /** Details of the project the template will run in. */
+    'project': {
+        /** The ID of the project to use. */
         'id': string;
-        /** The name of the template Example: "Example Template" */
-        'name': string;
-    };
-    /** Status of the template run. Example: "success" */
-    'status': 'waiting' | 'failure' | 'retrying' | 'success' | 'unknown';
-    /** Details about the template run. */
-    'content': {
-        /** Name of the template. Example: "Example Template" */
-        'name': string;
-        /** Description of the template. Example: "This is a sample template." */
-        'description'?: string;
-        /** The version of the Northflank API to run the template against. Example: "v1" */
-        'apiVersion': 'v1';
-        /** Details of the project the template will run in. */
-        'project': {
-            /** The ID of the project to use. */
-            'id': string;
+    } | {
+        'spec': {
+            /** The name of the project. Example: "New Project" */
+            'name': string;
+            /** The description of the project. Example: "This is a new project." */
+            'description'?: string;
+            /** The color of the project in the Northflank App. Example: "#EF233C" */
+            'color'?: string;
+            /** The region the project will be hosted in. Example: "europe-west" */
+            'region': string;
         } | {
-            'spec': {
-                /** The name of the project. Example: "New Project" */
-                'name': string;
-                /** The description of the project. Example: "This is a new project." */
-                'description'?: string;
-                /** The color of the project in the Northflank App. Example: "#EF233C" */
-                'color'?: string;
-                /** The region the project will be hosted in. Example: "europe-west" */
-                'region': string;
-            } | {
-                /** The name of the project. Example: "New Project" */
-                'name': string;
-                /** The description of the project. Example: "This is a new project." */
-                'description'?: string;
-                /** The color of the project in the Northflank App. Example: "#EF233C" */
-                'color'?: string;
-                /** The BYOC cluster this project will be hosted in. Example: "gcp-cluster-1" */
-                'clusterId'?: string;
-            };
+            /** The name of the project. Example: "New Project" */
+            'name': string;
+            /** The description of the project. Example: "This is a new project." */
+            'description'?: string;
+            /** The color of the project in the Northflank App. Example: "#EF233C" */
+            'color'?: string;
+            /** The BYOC cluster this project will be hosted in. Example: "gcp-cluster-1" */
+            'clusterId'?: string;
         };
-        /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
-        'arguments'?: any;
-        'refs'?: any;
-        'spec': any;
     };
+    /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
+    'arguments'?: any;
+    'spec': any;
+    'refs'?: any;
+    /** Identifier for the template run Example: "3dd592f6-ce63-45ee-acf8-13dc5ec5235c" */
+    'id': string;
+    /** Identifier for the template Example: "example-template" */
+    'templateId': string;
+    /** Status of the template run Example: "pending" */
+    'status': 'pending' | 'running' | 'success' | 'failure';
+    /** time of creation */
+    'createdAt'?: string;
+    /** time of update */
+    'updatedAt'?: string;
 };
 declare type RunTemplateCall = (opts: RunTemplateRequest) => Promise<ApiCallResponse<RunTemplateResult>>;
 declare type RunTemplateRequest = {
@@ -12022,30 +12403,22 @@ declare class RunTemplateEndpoint extends PostApiEndpoint<RunTemplateRequest, Ru
 declare type ListTemplaterunsResult = {
     /** An array of template run objects. */
     'templateRuns': {
-        /** ID of the template run. Example: "501c1e03-a021-4659-9048-85f8f6ee2bc7" */
+        /** Name of the template. Example: "Example Template" */
+        'name': string;
+        /** Description of the template. Example: "This is a sample template." */
+        'description'?: string;
+        /** The version of the Northflank API to run the template against. Example: "v1" */
+        'apiVersion': 'v1';
+        /** Identifier for the template run Example: "3dd592f6-ce63-45ee-acf8-13dc5ec5235c" */
         'id': string;
-        /** Timestamp of when the run was initiated. Example: "2022-06-14 15:10:42.842Z" */
-        'createdAt': string;
-        /** Timestamp of when the run was last updated. Example: "2022-06-14 15:10:42.842Z" */
-        'updatedAt': string;
-        /** Details about the template being run. */
-        'template': {
-            /** ID of the template Example: "example-template" */
-            'id': string;
-            /** The name of the template Example: "Example Template" */
-            'name': string;
-        };
-        /** Details about the template run. */
-        'content': {
-            /** Name of the template. Example: "Example Template" */
-            'name': string;
-            /** Description of the template. Example: "This is a sample template." */
-            'description'?: string;
-            /** The version of the Northflank API to run the template against. Example: "v1" */
-            'apiVersion': 'v1';
-        };
-        /** Status of the template run. Example: "success" */
-        'status': 'waiting' | 'failure' | 'retrying' | 'success' | 'unknown';
+        /** Identifier for the template Example: "example-template" */
+        'templateId': string;
+        /** Status of the template run Example: "pending" */
+        'status': 'pending' | 'running' | 'success' | 'failure';
+        /** time of creation */
+        'createdAt'?: string;
+        /** time of update */
+        'updatedAt'?: string;
     }[];
 };
 declare type ListTemplaterunsCall = (opts: ListTemplaterunsRequest) => Promise<ApiCallResponse<ListTemplaterunsResult>>;
@@ -12074,59 +12447,51 @@ declare class ListTemplaterunsEndpoint extends GetApiEndpoint<ListTemplaterunsRe
 }
 
 declare type GetTemplaterunResult = {
-    /** ID of the template run. Example: "501c1e03-a021-4659-9048-85f8f6ee2bc7" */
-    'id': string;
-    /** Timestamp of when the run was initiated. Example: "2022-06-14 15:10:42.842Z" */
-    'createdAt': string;
-    /** Timestamp of when the run was last updated. Example: "2022-06-14 15:10:42.842Z" */
-    'updatedAt': string;
-    /** Details about the template being run. */
-    'template': {
-        /** ID of the template Example: "example-template" */
+    /** Name of the template. Example: "Example Template" */
+    'name': string;
+    /** Description of the template. Example: "This is a sample template." */
+    'description'?: string;
+    /** The version of the Northflank API to run the template against. Example: "v1" */
+    'apiVersion': 'v1';
+    /** Details of the project the template will run in. */
+    'project': {
+        /** The ID of the project to use. */
         'id': string;
-        /** The name of the template Example: "Example Template" */
-        'name': string;
-    };
-    /** Status of the template run. Example: "success" */
-    'status': 'waiting' | 'failure' | 'retrying' | 'success' | 'unknown';
-    /** Details about the template run. */
-    'content': {
-        /** Name of the template. Example: "Example Template" */
-        'name': string;
-        /** Description of the template. Example: "This is a sample template." */
-        'description'?: string;
-        /** The version of the Northflank API to run the template against. Example: "v1" */
-        'apiVersion': 'v1';
-        /** Details of the project the template will run in. */
-        'project': {
-            /** The ID of the project to use. */
-            'id': string;
+    } | {
+        'spec': {
+            /** The name of the project. Example: "New Project" */
+            'name': string;
+            /** The description of the project. Example: "This is a new project." */
+            'description'?: string;
+            /** The color of the project in the Northflank App. Example: "#EF233C" */
+            'color'?: string;
+            /** The region the project will be hosted in. Example: "europe-west" */
+            'region': string;
         } | {
-            'spec': {
-                /** The name of the project. Example: "New Project" */
-                'name': string;
-                /** The description of the project. Example: "This is a new project." */
-                'description'?: string;
-                /** The color of the project in the Northflank App. Example: "#EF233C" */
-                'color'?: string;
-                /** The region the project will be hosted in. Example: "europe-west" */
-                'region': string;
-            } | {
-                /** The name of the project. Example: "New Project" */
-                'name': string;
-                /** The description of the project. Example: "This is a new project." */
-                'description'?: string;
-                /** The color of the project in the Northflank App. Example: "#EF233C" */
-                'color'?: string;
-                /** The BYOC cluster this project will be hosted in. Example: "gcp-cluster-1" */
-                'clusterId'?: string;
-            };
+            /** The name of the project. Example: "New Project" */
+            'name': string;
+            /** The description of the project. Example: "This is a new project." */
+            'description'?: string;
+            /** The color of the project in the Northflank App. Example: "#EF233C" */
+            'color'?: string;
+            /** The BYOC cluster this project will be hosted in. Example: "gcp-cluster-1" */
+            'clusterId'?: string;
         };
-        /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
-        'arguments'?: any;
-        'refs'?: any;
-        'spec': any;
     };
+    /** A set of arguments that can be referenced in a template using '${args.argumentName}'. */
+    'arguments'?: any;
+    'spec': any;
+    'refs'?: any;
+    /** Identifier for the template run Example: "3dd592f6-ce63-45ee-acf8-13dc5ec5235c" */
+    'id': string;
+    /** Identifier for the template Example: "example-template" */
+    'templateId': string;
+    /** Status of the template run Example: "pending" */
+    'status': 'pending' | 'running' | 'success' | 'failure';
+    /** time of creation */
+    'createdAt'?: string;
+    /** time of update */
+    'updatedAt'?: string;
 };
 declare type GetTemplaterunCall = (opts: GetTemplaterunRequest) => Promise<ApiCallResponse<GetTemplaterunResult>>;
 declare type GetTemplaterunRequest = {