PR - (#174) feat: ipsec_tunnel_status check Proxy ID support #320

Sign in to view logs

Triggered via pull request October 29, 2024 14:42

alperenkose

opened #174

ipsec-tunnel-status-proxyids

Status Success

Total duration 1m 22s

Artifacts 3

pr.yml

on: pull_request

Discover minimum Python version / Discover minimum Python version

Upload PR details to artifact

Formatting and security / Verify code formatting and security

Unit Tests / Verify unit tests are successful

API documentation / Verify if generated API documentation is up to date

Build Docker image / Build a Docker image

Fetch the updated documentation

Annotations

4 warnings and 10 notices

API documentation / Verify if generated API documentation is up to date

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, Gr1N/setup-poetry@v8. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Formatting and security / Verify code formatting and security

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, Gr1N/setup-poetry@v8. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Unit Tests / Verify unit tests are successful

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, Gr1N/setup-poetry@v8. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Build Docker image / Build a Docker image

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, Gr1N/setup-poetry@v8. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Unit Tests / Verify unit tests are successful

Starting action

Unit Tests / Verify unit tests are successful

HTTP Request: GET https://api.github.com/repos/PaloAltoNetworks/pan-os-upgrade-assurance "HTTP/1.1 200 OK"

Unit Tests / Verify unit tests are successful

Generating comment for PR

Unit Tests / Verify unit tests are successful

HTTP Request: GET https://api.github.com/repos/PaloAltoNetworks/pan-os-upgrade-assurance/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 404 Not Found"

Unit Tests / Verify unit tests are successful

HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"

Unit Tests / Verify unit tests are successful

HTTP Request: GET https://api.github.com/repos/PaloAltoNetworks/pan-os-upgrade-assurance/issues/174/comments "HTTP/1.1 200 OK"

Unit Tests / Verify unit tests are successful

Adding new comment

Unit Tests / Verify unit tests are successful

HTTP Request: POST https://api.github.com/repos/PaloAltoNetworks/pan-os-upgrade-assurance/issues/174/comments "HTTP/1.1 403 Forbidden"

Unit Tests / Verify unit tests are successful

Cannot post comment. This is probably because this is an external PR, so it's expected. Ensure you have an additional `workflow_run` step configured as explained in the documentation (or alternatively, give up on PR comments for external PRs).

Unit Tests / Verify unit tests are successful

Ending action

Artifacts

Produced during runtime

Name	Size
documentation	37.2 KB
pr	263 Bytes
python-coverage-comment-action	1.14 KB