Skip to content

Update Faq #10913

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 16, 2025
Merged

Update Faq #10913

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a50843e
Update Faq
vishal-av Jul 15, 2025
16904e0
Update runtime versions
vishal-av Jul 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/continuous-delivery/deploy-srv-diff-platforms/aws/aws-sam-deployments.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,9 +85,9 @@ We recommend you to use the new images that we have introduced with multiple run

### New SAM Images

Harness support [multiple runtime images](https://hub.docker.com/r/harness/aws-sam-plugin/tags) for **nodejs20**, **nodejs18**, **python3.11**, **python3.12**, **ruby3.2**, **java8**, **go1.22** and **java17**.. These are Linux AMD64 images.
Harness support [multiple runtime images](https://hub.docker.com/r/harness/aws-sam-plugin/tags) for **nodejs22**, **nodejs20**, **nodejs18**, **python3.11**, **python3.12**, **ruby3.2**, **java 21**,**java17**, **java8** and **go1.22**. These are Linux AMD64 images.

Unlike old images, in new images a single image has the capabiliity of handling all the SAM steps.
Unlike old images, in new images a single image has the capability of handling all the SAM steps.

Runtimes | Images | Version
| --- | --- | --- |
Expand Down
17 changes: 11 additions & 6 deletions docs/continuous-delivery/manage-deployments/deployment-faqs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,13 +128,18 @@ For more details, go to [Steady state check](https://developer.harness.io/docs/c
Workflow notification strategy can only interpret Condition,Scope, and User Group fields. So, all the notification rules are applied on workflow level.


### Is it possible to modify the looping stage runs inside a pipeline execution?
### Can I customize the names of looping stage runs in a pipeline execution?

You can use Matrix strategies where you can use labels. To use the matrix labels naming strategy, do the following:
1. In Harness, select Account Settings.
2. Select Account Resources, then select Pipeline.
3. Set Enable Matrix Labels By Name to true.
4. Select Save.
Yes, you can. Harness uses a default matrix naming strategy that labels looping stages with numeric indices (like _2_2, _1_3, etc.). To make these names more readable, you can enable matrix labels based on axis names.

To enable this:
1. In Harness, go to Account Settings.
2. Navigate to Default Settings at the Account, Organization, or Project level.
3. Expand Pipeline settings.
4. Set **Enable Matrix Labels By Name** to **true**.
5. Select **Save**.

For more information, refer [Looping Strategies](/docs/platform/pipelines/looping-strategies/looping-strategies-matrix-repeat-and-parallelism/#customize-matrix-stage-names).


### How do you determine the number of service instances/licenses for our services?
Expand Down