build: Upgrade trustify-da-api-spec 2.0.1 and trustify-da-java-client 0.0.11

[soul2zimate]

• build: Upgrade trustify-da-api-spec 2.0.2 and trustify-da-java-client 0.0.11
• feat: update to trustify-da

fixes: #224

Hi @ruromero I am making this as draft, I need to wait for the v5 endpoint deployed and ready before I can merge this, right ?

[ruromero]

You're missing to set the TRUSTIFY_DA_BACKEND_URL that now has to be set. It must point to rhda.rhcloud.com

[ruromero]

• build: Upgrade trustify-da-api-spec 2.0.1 and trustify-da-java-client 0.0.9
• feat: update to trustify-da

fixes: #224

Hi @ruromero I am making this as draft, I need to wait for the v5 endpoint deployed and ready before I can merge this, right ?

The v5 endpoint is available on stage already

[soul2zimate]

You're missing to set the TRUSTIFY_DA_BACKEND_URL that now has to be set. It must point to rhda.rhcloud.com

Thanks. I have updated the PR to set the required TRUSTIFY_DA_BACKEND_URL .

The v5 endpoint is available on stage already

OK, I can test against v5 stage URL. But if I merge this it will be published to nightly build before the prod backend service gets ready.

[ruromero]

Looks good. Thank you

[ruromero]

You're missing to set the TRUSTIFY_DA_BACKEND_URL that now has to be set. It must point to rhda.rhcloud.com

Thanks. I have updated the PR to set the required TRUSTIFY_DA_BACKEND_URL .

The v5 endpoint is available on stage already

OK, I can test against v5 stage URL. But if I merge this it will be published to nightly build before the prod backend service gets ready.

We should indeed wait until the backend is deployed in prod. Thanks for noticing

[soul2zimate]

Hi @ruromero how about this one? Should I merge or wait until the deployments are ready?

[ruromero]

this will end up creating a nightly that won't work so it must wait

[soul2zimate]

since last update, I have upgraded trustify-da-api-spec 2.0.2 and trustify-da-java-client 0.0.11

I also tested against latest tpa and da stages and fixes two issues:

• NPE when issue.getRemediation() return null (no remediation available from report)
• eliminate duplicate vulnerability annotations in CAAnnotator

please review when you have time next week and remove the "hold", then I will merge this one. Thanks.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[soul2zimate]

@ruromero Thank you for the review