making sure create role perm is given for the new resource #3478
TOEL2cicd-1-pull-request.yaml
on: pull_request
Set CI/CD metadata
7s
Commit stage
/
Scan secrets
9s
Commit stage
/
Check file format
11s
Commit stage
/
Check Markdown format
5s
Commit stage
/
Check English usage
7s
Commit stage
/
Lint Terraform
8s
Commit stage
/
Checkov Terraform
32s
Commit stage
/
Count lines of code
22s
Commit stage
/
Scan dependencies
52s
Commit stage
/
OWASP Dependency Scan
34s
Commit stage
/
Check for dead code
34s
Acceptance stage
/
Contract test
4s
Acceptance stage
/
Security test
4s
Acceptance stage
/
UI test
6s
Acceptance stage
/
UI performance test
3s
Acceptance stage
/
Integration test
2m 30s
Acceptance stage
/
Accessibility test
3s
Acceptance stage
/
Load test
6s
Acceptance stage
/
Environment tear down
5s
Annotations
5 warnings
|
Commit stage / Count lines of code
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Commit stage / OWASP Dependency Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: github/codeql-action/upload-sarif@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Commit stage / OWASP Dependency Scan
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
|
|
Commit stage / Scan dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Acceptance stage / Integration test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: phoenix-actions/test-reporting@v15. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
coverage.xml
|
7.28 KB |
sha256:92595b4e3cf08980d3c0f9dfa47dc98b3ce69a838b8e4bf7172b05c900a001e2
|
|
|
integration-test-results
|
2.33 KB |
sha256:30a65bc0146d90330022cd6f046172a2cccf4672ce5118acf444b66bb181e44a
|
|
|
lambda
|
19.2 MB |
sha256:1b2765e4932046a93734d93e47a5e312b4b4e324521eec9c4c65d065a6d80a84
|
|
|
lines-of-code-report-.json.zip
|
838 Bytes |
sha256:dfaaf7d6810d157e9cdba6703a5dfe6b8934938ddec3c35cb33b4af1c5dd02aa
|
|
|
sbom-repository-report.json.zip
|
58.8 KB |
sha256:a930c801b1412621b82d77039514b86fe9d7784cc0f04a82ec58347f3c5d8e90
|
|
|
vulnerabilities-repository-report-.json.zip
|
4.61 KB |
sha256:7d2526c2e502cc66833381e3be18821224a7cc054c676c48ddc19c2f38a1cd25
|
|