Update specifications.md

NimRegev · NimRegev · commit fb8171af95c2 · 2025-05-13T10:05:06.000+03:00
diff --git a/_docs/pipelines/specifications.md b/_docs/pipelines/specifications.md
@@ -92,8 +92,8 @@ The priority (override behavior) is as follows, from highest to lowest:
 | `spec.requiredAvailableStorage`    | The minimum disk space for the pipeline’s build volume in `Gi`. <br> When defined, Codefresh assigns either a cached disk with sufficient disk space or a new empty disk at the start of the build. <br>When empty, only the space not allocated for caching is available for the build volume. <br>See [Set minimum disk space for a pipeline build]({{site.baseurl}}/docs/pipelines/pipelines/#set-minimum-disk-space-for-a-pipeline-build).  | string    | Optional |
 | `spec.lowMemoryWarningThreshold`    | The memory-usage threshold for the pipeline's build exceeding which to display banner alerts. Useful to get timely warnings and prevent build failures. <br>Can be one of the following:{::nomarkdown}<ul><li><b>WARNING</b>: Displays a banner when memory usage exceeds 70% of the available memory. </li><li><b>CRITICAL</b>: Displays a banner when memory usage exceeds 90% of the available memory. </li><li><b>REACHED_LIMIT</b>: Displays a banner when memory usage exceeds 100% of the available memory. Setting this threshold means that the pipeline build has already failed when the banner is displayed.</li></ul>{:/}See also [Set memory usage threshold for pipeline build]({{site.baseurl}}/docs/pipelines/pipelines/#set-memory-usage-threshold-for-pipeline-build).| string    | Optional|
 | `spec.packId`    | Required for SaaS environments. Optional for hybrid environments.<br>The package identifier based on the resource size. Can be one of the following:{::nomarkdown}<ul><li><code class="highlighter-rouge">5cd1746617313f468d669013</code>: Small</li><li><code class="highlighter-rouge">5cd1746717313f468d669014</code>: Medium</li><li><code class="highlighter-rouge">5cd1746817313f468d669015</code>: Large</li><li><code class="highlighter-rouge">5cd1746817313f468d669017</code>: Extra large</li><li><code class="highlighter-rouge">5cd1746817313f468d669018</code>: XXL</li><li><code class="highlighter-rouge">5cd1746817313f468d669020</code>: 4XL</li></ul>{:/} | string | Required (for SaaS) |
-| `spec.contexts`    | Single or multiple comma-separated shared configuration contexts, including shared secrets to add to the pipeline. <br>See [Shared configuration contexts]({{site.baseurl}}/docs/pipelines/configuration/shared-configuration/).   | array   | Optional |
-| `spec.clustersInfo`    | Determines if all or specific Kubernetes clusters are available for the pipeline build. Leave empty to inherit the account-level setting. (NIMA: how can the user know what the account-level setting is? Do they have to go manually to the Settings to see if there are restrictions?) <br>See [Select Kubernetes cluster contexts]({{site.baseurl}}/docs/pipelines/pipelines/#select-kubernetes-cluster-contexts).  | object  | Optional |
+| `spec.context`    | Single or multiple comma-separated shared configuration contexts, including shared secrets to add to the pipeline. <br>See [Shared configuration contexts]({{site.baseurl}}/docs/pipelines/configuration/shared-configuration/).   | array   | Optional |
+| `spec.clustersInfo`    | Determines if all or specific Kubernetes clusters are available for the pipeline build. Leave empty to inherit the account-level setting. <!--- how can the user know what the account-level setting is? Do they have to go manually to the Settings to see if there are restrictions? --> <br>See [Select Kubernetes cluster contexts]({{site.baseurl}}/docs/pipelines/pipelines/#select-kubernetes-cluster-contexts).  | object  | Optional |
 | `spec.variables`    | The variables defined in the pipeline. See [spec.variables](#specvariables). | array    | Optional |
 | `spec.specTemplate`    | See [spec.specTemplate](#specspectemplate). | object    | Optional |
 | `spec.steps`    | The steps to be executed by the pipeline, as a list of key-value pairs. <br>See [Steps in pipelines]({{site.baseurl}}/docs/pipelines/steps/). | object    | Required |
@@ -141,6 +141,7 @@ The priority (override behavior) is as follows, from highest to lowest:
 | `spec.triggers.gerritCIStatusLabels`       | The labels indicating the CI status. | array | Optional  |
 | `spec.triggers.context`       | The name of the Git integration to use.  | string | Optional |
 | `spec.triggers.concurrency`   | The maximum number of concurrent builds for this trigger, and can range from `1` (the default), to `15`, or unlimited). Define the trigger concurrency when your pipeline has multiple triggers. | string | Optional |
+| `spec.triggers.priority`   | ?? | integer | Optional |
 | `spec.triggers.terminationPolicy`   | The options that determine when to terminate the build from the pipeline. See [spec.terminationPolicy](#specterminationpolicy). | integer | Optional |
 
 
