ami auto update

spotinst · Jan 8, 2024 · dee8519 · dee8519
1 parent 9709241
commit dee8519
Showing 1 changed file with 48 additions and 1 deletion.
diff --git a/api/services/ocean/aws/schemas/ocean-scheduling.yaml b/api/services/ocean/aws/schemas/ocean-scheduling.yaml
@@ -29,7 +29,7 @@ properties:
         taskType:
           type: string
           example: clusterRoll
-          enum: ["clusterRoll"]
+          enum: ["clusterRoll", "amiAutoUpdate"]
           description: >
             The activity that you are scheduling. Valid values: "clusterRoll". Required for cluster.scheduling.tasks.
         parameters:
@@ -64,6 +64,53 @@ properties:
                     During the roll, if the parameter is set to true we honor PDB during the instance replacement.
                   example: true
                   default: false
+            amiAutoUpdate:
+              type: object
+              properties:
+                patch:
+                  type: boolean
+                  description: >
+                    Update AMI if a newer patch version is available.
+                  example: "true"
+                minorVersion:
+                  type: boolean
+                  example: "true"
+                  description: >
+                    Update AMI if a newer AMI minor version is available.
+                applyRoll:
+                  type: boolean
+                  example: "true"
+                  description: >
+                    Apply a cluster roll after an AMI was updated.
+                clusterRoll:
+                  type: object
+                  properties:
+                    batchSizePercentage:
+                      type: integer
+                      minimum: 0
+                      maximum: 100
+                      example: 20
+                      description: >
+                        Value as a percent to set the size of a batch in a roll. Valid values are 0-100.
+                    comment:
+                      type: string
+                      example: This is why I deployed my cluster.
+                      description: >
+                        Add a comment description for the roll. The comment is limited to 256 chars
+                    batchMinHealthyPercentage:
+                      type: integer
+                      minimum: 1
+                      maximum: 100
+                      default: 50
+                      example: 100
+                      description: >
+                        Indicates the threshold of minimum healthy instances in single batch. If the amount of healthy instances in single batch is under the threshold, the cluster roll will fail. If exists, the parameter value will be in range of 1-100. In case of null as value, the default value in the backend will be 50%. Value of param should represent the number in percentage (%) of the batch.
+                    respectPdb:
+                      type: boolean
+                      description: >
+                        During the roll, if the parameter is set to true we honor PDB during the instance replacement.
+                      example: true
+                      default: false
   shutdownHours:
     type: object
     description: >