Skip to content

[RFC] Fix https-only config #198

[RFC] Fix https-only config

[RFC] Fix https-only config #198

Triggered via pull request October 17, 2024 17:49
Status Success
Total duration 37m 31s
Artifacts

pr_test_e2e_extra.yaml

on: pull_request
Run e2e tests for extra scenarios  /  Run checks
37m 21s
Run e2e tests for extra scenarios / Run checks
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Run e2e tests for extra scenarios / Run checks
The following actions uses node12 which is deprecated and will be forced to run on node16: azure/setup-helm@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run e2e tests for extra scenarios / Run checks
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, azure/setup-helm@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run e2e tests for extra scenarios / Run checks
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/