qovery-typescript-axios 1.1.1018 → 1.1.1019
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/api.ts +43 -0
- package/dist/api.d.ts +43 -0
- package/dist/esm/api.d.ts +43 -0
- package/package.json +1 -1
package/api.ts
CHANGED
|
@@ -5796,6 +5796,43 @@ export interface BuildSettings {
|
|
|
5796
5796
|
*/
|
|
5797
5797
|
'skip_git_submodules'?: boolean;
|
|
5798
5798
|
}
|
|
5799
|
+
/**
|
|
5800
|
+
* Resources the builder used during this build, image push and cache export included. Only set on BUILD. Compare them with the service\'s build CPU and memory settings. The four usage fields come together, or are all absent when no sample was taken (a build shorter than the sampling interval, or a cluster without a metrics API).
|
|
5801
|
+
* @export
|
|
5802
|
+
* @interface BuilderUsage
|
|
5803
|
+
*/
|
|
5804
|
+
export interface BuilderUsage {
|
|
5805
|
+
/**
|
|
5806
|
+
* Highest CPU use seen, in millicores.
|
|
5807
|
+
* @type {number}
|
|
5808
|
+
* @memberof BuilderUsage
|
|
5809
|
+
*/
|
|
5810
|
+
'cpu_milli_max'?: number;
|
|
5811
|
+
/**
|
|
5812
|
+
* Average CPU use over the samples, in millicores.
|
|
5813
|
+
* @type {number}
|
|
5814
|
+
* @memberof BuilderUsage
|
|
5815
|
+
*/
|
|
5816
|
+
'cpu_milli_avg'?: number;
|
|
5817
|
+
/**
|
|
5818
|
+
* Highest memory use seen, in MiB.
|
|
5819
|
+
* @type {number}
|
|
5820
|
+
* @memberof BuilderUsage
|
|
5821
|
+
*/
|
|
5822
|
+
'memory_mib_max'?: number;
|
|
5823
|
+
/**
|
|
5824
|
+
* Number of samples the values above come from. Usage is sampled periodically, so a short build has few samples and its peaks can be missed.
|
|
5825
|
+
* @type {number}
|
|
5826
|
+
* @memberof BuilderUsage
|
|
5827
|
+
*/
|
|
5828
|
+
'samples'?: number;
|
|
5829
|
+
/**
|
|
5830
|
+
* Present, and true, only when the builder was killed for running out of memory. Absent otherwise: never test it against false. Raising the build memory setting fixes it.
|
|
5831
|
+
* @type {boolean}
|
|
5832
|
+
* @memberof BuilderUsage
|
|
5833
|
+
*/
|
|
5834
|
+
'oom_killed'?: boolean;
|
|
5835
|
+
}
|
|
5799
5836
|
/**
|
|
5800
5837
|
*
|
|
5801
5838
|
* @export
|
|
@@ -26883,6 +26920,12 @@ export interface ServiceStepMetric {
|
|
|
26883
26920
|
* @memberof ServiceStepMetric
|
|
26884
26921
|
*/
|
|
26885
26922
|
'sub_steps'?: Array<ServiceSubStepMetric>;
|
|
26923
|
+
/**
|
|
26924
|
+
*
|
|
26925
|
+
* @type {BuilderUsage}
|
|
26926
|
+
* @memberof ServiceStepMetric
|
|
26927
|
+
*/
|
|
26928
|
+
'builder_usage'?: BuilderUsage;
|
|
26886
26929
|
}
|
|
26887
26930
|
|
|
26888
26931
|
|
package/dist/api.d.ts
CHANGED
|
@@ -5620,6 +5620,43 @@ export interface BuildSettings {
|
|
|
5620
5620
|
*/
|
|
5621
5621
|
'skip_git_submodules'?: boolean;
|
|
5622
5622
|
}
|
|
5623
|
+
/**
|
|
5624
|
+
* Resources the builder used during this build, image push and cache export included. Only set on BUILD. Compare them with the service\'s build CPU and memory settings. The four usage fields come together, or are all absent when no sample was taken (a build shorter than the sampling interval, or a cluster without a metrics API).
|
|
5625
|
+
* @export
|
|
5626
|
+
* @interface BuilderUsage
|
|
5627
|
+
*/
|
|
5628
|
+
export interface BuilderUsage {
|
|
5629
|
+
/**
|
|
5630
|
+
* Highest CPU use seen, in millicores.
|
|
5631
|
+
* @type {number}
|
|
5632
|
+
* @memberof BuilderUsage
|
|
5633
|
+
*/
|
|
5634
|
+
'cpu_milli_max'?: number;
|
|
5635
|
+
/**
|
|
5636
|
+
* Average CPU use over the samples, in millicores.
|
|
5637
|
+
* @type {number}
|
|
5638
|
+
* @memberof BuilderUsage
|
|
5639
|
+
*/
|
|
5640
|
+
'cpu_milli_avg'?: number;
|
|
5641
|
+
/**
|
|
5642
|
+
* Highest memory use seen, in MiB.
|
|
5643
|
+
* @type {number}
|
|
5644
|
+
* @memberof BuilderUsage
|
|
5645
|
+
*/
|
|
5646
|
+
'memory_mib_max'?: number;
|
|
5647
|
+
/**
|
|
5648
|
+
* Number of samples the values above come from. Usage is sampled periodically, so a short build has few samples and its peaks can be missed.
|
|
5649
|
+
* @type {number}
|
|
5650
|
+
* @memberof BuilderUsage
|
|
5651
|
+
*/
|
|
5652
|
+
'samples'?: number;
|
|
5653
|
+
/**
|
|
5654
|
+
* Present, and true, only when the builder was killed for running out of memory. Absent otherwise: never test it against false. Raising the build memory setting fixes it.
|
|
5655
|
+
* @type {boolean}
|
|
5656
|
+
* @memberof BuilderUsage
|
|
5657
|
+
*/
|
|
5658
|
+
'oom_killed'?: boolean;
|
|
5659
|
+
}
|
|
5623
5660
|
/**
|
|
5624
5661
|
*
|
|
5625
5662
|
* @export
|
|
@@ -26097,6 +26134,12 @@ export interface ServiceStepMetric {
|
|
|
26097
26134
|
* @memberof ServiceStepMetric
|
|
26098
26135
|
*/
|
|
26099
26136
|
'sub_steps'?: Array<ServiceSubStepMetric>;
|
|
26137
|
+
/**
|
|
26138
|
+
*
|
|
26139
|
+
* @type {BuilderUsage}
|
|
26140
|
+
* @memberof ServiceStepMetric
|
|
26141
|
+
*/
|
|
26142
|
+
'builder_usage'?: BuilderUsage;
|
|
26100
26143
|
}
|
|
26101
26144
|
/**
|
|
26102
26145
|
* The name of the deployment step at the service level: - REGISTRY_CREATE_REPOSITORY: The step to create the repository in the registry. - GIT_CLONE: The step to clone the source code repository. - BUILD_QUEUEING: The queuing time preceding the actual building step. - BUILD: The step to build the source code. - DEPLOYMENT_QUEUEING: The queuing time preceding the actual deployment step. - DEPLOYMENT: The step to deploy the service. - ROUTER_DEPLOYMENT: The step to deploy the router. - MIRROR_IMAGE: The step to mirror the image to the private registry. - EXECUTING: The step to execute a job or terraform apply.
|
package/dist/esm/api.d.ts
CHANGED
|
@@ -5620,6 +5620,43 @@ export interface BuildSettings {
|
|
|
5620
5620
|
*/
|
|
5621
5621
|
'skip_git_submodules'?: boolean;
|
|
5622
5622
|
}
|
|
5623
|
+
/**
|
|
5624
|
+
* Resources the builder used during this build, image push and cache export included. Only set on BUILD. Compare them with the service\'s build CPU and memory settings. The four usage fields come together, or are all absent when no sample was taken (a build shorter than the sampling interval, or a cluster without a metrics API).
|
|
5625
|
+
* @export
|
|
5626
|
+
* @interface BuilderUsage
|
|
5627
|
+
*/
|
|
5628
|
+
export interface BuilderUsage {
|
|
5629
|
+
/**
|
|
5630
|
+
* Highest CPU use seen, in millicores.
|
|
5631
|
+
* @type {number}
|
|
5632
|
+
* @memberof BuilderUsage
|
|
5633
|
+
*/
|
|
5634
|
+
'cpu_milli_max'?: number;
|
|
5635
|
+
/**
|
|
5636
|
+
* Average CPU use over the samples, in millicores.
|
|
5637
|
+
* @type {number}
|
|
5638
|
+
* @memberof BuilderUsage
|
|
5639
|
+
*/
|
|
5640
|
+
'cpu_milli_avg'?: number;
|
|
5641
|
+
/**
|
|
5642
|
+
* Highest memory use seen, in MiB.
|
|
5643
|
+
* @type {number}
|
|
5644
|
+
* @memberof BuilderUsage
|
|
5645
|
+
*/
|
|
5646
|
+
'memory_mib_max'?: number;
|
|
5647
|
+
/**
|
|
5648
|
+
* Number of samples the values above come from. Usage is sampled periodically, so a short build has few samples and its peaks can be missed.
|
|
5649
|
+
* @type {number}
|
|
5650
|
+
* @memberof BuilderUsage
|
|
5651
|
+
*/
|
|
5652
|
+
'samples'?: number;
|
|
5653
|
+
/**
|
|
5654
|
+
* Present, and true, only when the builder was killed for running out of memory. Absent otherwise: never test it against false. Raising the build memory setting fixes it.
|
|
5655
|
+
* @type {boolean}
|
|
5656
|
+
* @memberof BuilderUsage
|
|
5657
|
+
*/
|
|
5658
|
+
'oom_killed'?: boolean;
|
|
5659
|
+
}
|
|
5623
5660
|
/**
|
|
5624
5661
|
*
|
|
5625
5662
|
* @export
|
|
@@ -26097,6 +26134,12 @@ export interface ServiceStepMetric {
|
|
|
26097
26134
|
* @memberof ServiceStepMetric
|
|
26098
26135
|
*/
|
|
26099
26136
|
'sub_steps'?: Array<ServiceSubStepMetric>;
|
|
26137
|
+
/**
|
|
26138
|
+
*
|
|
26139
|
+
* @type {BuilderUsage}
|
|
26140
|
+
* @memberof ServiceStepMetric
|
|
26141
|
+
*/
|
|
26142
|
+
'builder_usage'?: BuilderUsage;
|
|
26100
26143
|
}
|
|
26101
26144
|
/**
|
|
26102
26145
|
* The name of the deployment step at the service level: - REGISTRY_CREATE_REPOSITORY: The step to create the repository in the registry. - GIT_CLONE: The step to clone the source code repository. - BUILD_QUEUEING: The queuing time preceding the actual building step. - BUILD: The step to build the source code. - DEPLOYMENT_QUEUEING: The queuing time preceding the actual deployment step. - DEPLOYMENT: The step to deploy the service. - ROUTER_DEPLOYMENT: The step to deploy the router. - MIRROR_IMAGE: The step to mirror the image to the private registry. - EXECUTING: The step to execute a job or terraform apply.
|