You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test runs:
https://github.com/splunk/splunk-add-on-for-amazon-web-services/actions/runs/9269557494https://github.com/splunk/test-addonfactory-repo/actions/runs/9270329208
Changes possibly affecting customers:
- add ui_marker to enable splitting UI tests execution
- fix for failing upload-artifact@v4 due to multiple artifacts with same
name
- replace edplato/trufflehog-actions-scan action with official
trufflehog action latest release
- bump version of workflow-engine-base image to v4.0 (Ubuntu 20 ->
Ubuntu 22)
Changes not affecting customers:
- wfe-test-runner-action update to v5 and change of the way that browser
is determined in k8s
- docs and ci related updates
Also note that starting from release v4.16.0 some assets are removed
from TA releases:
1. installation-actions.json
2. installation-update.json
3. \<TA-release\>-_forwarders.spl
4. \<TA-release\>-_indexers.spl
5. \<TA-release\>-_search_heads.spl
Copy file name to clipboardExpand all lines: README.md
+14-12Lines changed: 14 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -162,36 +162,31 @@ security-detect-secrets
162
162
163
163
**Description:**
164
164
165
-
- This action is intended as a Continuous Integration secret scan in an already "clean" repository. The default commit scan depth is the last 50 commits and can be adjusted using Custom Arguments
165
+
- This action is intended as a Continuous Integration secret scan in an already "clean" repository.
166
166
167
-
- The stage checks for addition/deletion of any secret/sensitive data in last 50 commits of the repository.
167
+
- The stage checks for addition/deletion of any secret/sensitive data in referenced commits (commits pushed or commits within PR).
- The stage is likely to fail if there is some sensitive or secrets or confidential data had been removed or added in the last 50 commits.
173
+
- The stage is likely to fail if any sensitive secrets or confidential data were removed or added in the referenced commits.
174
174
175
175
**Troubleshooting steps for failures if any**
176
176
177
177
- User would need to update the commit history where the sensitive information is detected.
178
178
179
179
**Exception File**
180
180
181
-
- To ignore the file add the path of the file having the false positive in the `.github/workflows/exclude-patterns.txt`, ideally this should be avoided and only specific false positives should be added in exception files.
181
+
- To ignore the file add the path of the file having the false positive in the `.github/workflows/exclude-patterns.txt`, ideally this should be avoided and only specific false positives should be added in exception files. This is file with newline separated regexes for files to exclude in scan.
182
182
183
183
- False positives include: public keys, random / dummy session keys or tokens.
184
184
185
-
- We can use this file `.github/workflows/trufflehog-false-positive.json` from action version `>=v0.9l-beta` to add specific failures or regexes.
186
-
187
-
- ref for how to add regex to json file : https://github.com/edplato/trufflehog-actions-scan#usage
188
-
189
-
-**NOTE:** The usage of `.github/workflows/trufflehog-false-positive.json` is not rolled out yet, PR for feature support: https://github.com/splunk/addonfactory-workflow-addon-release/pull/32
190
-
185
+
- User can add a `trufflehog:ignore` comment on the line containing the secret to ignore that secrets.
191
186
192
187
**Artifacts:**
193
188
194
-
- No additional artifacts, the commit info is available in the logs.
189
+
- No additional artifacts, the commit info and secrets details are available in the logs.
195
190
196
191
197
192
security-sast-semgrep
@@ -486,6 +481,9 @@ cim-compliance-report
486
481
**Description**
487
482
488
483
- This stage does the setup for executing UI tests and reports the results
484
+
- It is possible to parallelize UI tests execution by using pytest markers.
485
+
To do so, one must specify `ui_marker` parameter in buid-test-release.yml as in [example](https://github.com/splunk/splunk-add-on-for-amazon-web-services/blob/925fd189737507dd91cc5275c59a8b390550411c/.github/workflows/build-test-release.yml#L35).
486
+
Markers must be created prior and each test case must be marked (check [run-modinput-tests](#run-modinput-tests), and this [PR](https://github.com/splunk/splunk-add-on-for-amazon-web-services/pull/1237))
489
487
490
488
**Action used:**
491
489
- No action used
@@ -525,6 +523,10 @@ Junit XML file
525
523
**Description**
526
524
527
525
- This stage does the setup for executing Modinput tests and reports the results
526
+
- It is possible to parallelize Modinput tests execution by using pytest markers.
527
+
To do so, one must specify `marker` parameter in buid-test-release.yml as in [example](https://github.com/splunk/splunk-add-on-for-amazon-web-services/blob/603f37ee24565f23104c0297e55a0c72480f34c9/.github/workflows/build-test-release.yml#L33).
528
+
Markers must be created prior and each test case must be marked (check the following references: [ref1](https://github.com/splunk/splunk-add-on-for-amazon-web-services/blob/main/tests/modinput_functional/README-test.md),
# Runbook to publish multiple images of different Linux flavors and versions for scripted inputs tests
2
+
3
+
Once there is new Splunk release, and [matrix](https://github.com/splunk/addonfactory-test-matrix-action) is updated, we need to make sure that Splunk images for scripted inputs tests are created and published.
4
+
## Steps
5
+
6
+
### Update OS images
7
+
- check what OS are listed in definition of matrix in scripted inputs tests [here](https://github.com/splunk/addonfactory-workflow-addon-release/blob/v4.16/.github/workflows/reusable-build-test-release.yml#L1966)
8
+
- if any is missing in [ta-automation-docker-images](https://cd.splunkdev.com/taautomation/ta-automation-docker-images/-/tree/main/dockerfiles) then add new Dockerfile
9
+
10
+
### Create images and publish them to ECR
11
+
- figure out what version of Splunk is needed (sha) using go/fetcher
12
+
- trigger [pipeline](https://cd.splunkdev.com/taautomation/ta-automation-docker-images/-/pipelines/new) for every OS flavor separately
0 commit comments