CCM-17437: Zap update and bug fix#1067
Conversation
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: CCM-17437 |
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: CCM-17437 |
5176c0a to
4362460
Compare
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: CCM-17437 |
4362460 to
07e190d
Compare
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: CCM-17437 |
1 similar comment
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: CCM-17437 |
135e071 to
3ca6dca
Compare
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: CCM-17437 |
3ca6dca to
d70a28d
Compare
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: CCM-17437 |
Ian-Hodges
left a comment
There was a problem hiding this comment.
Is there any where we can see that the zap-report.xml is being generated correctly?
nodejs version update
Replace hbs-cli with handlers and added a script to replicate that
d70a28d to
0afa700
Compare
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: CCM-17437 |

Summary
Updated zapproxy version, python and nodejs. Replaced hbs-cli and used handlebars instead. Checked that the security analysis works ok.
https://dev.azure.com/NHSD-APIM/API%20Platform/_build/results?buildId=505891&view=results
Reviews Required
Checklist