[FOLIO-3382] Upgrade amf-client-js to v5 for api-lint Created: 10/Jan/22  Updated: 28/Apr/22  Resolved: 17/Jan/22

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: David Crossley Assignee: David Crossley
Resolution: Done Votes: 0
Labels: oas, raml
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-3486 Upgrade amf-client-js to v5.0.8 for a... Closed
relates to FOLIO-2893 Create folio-tools/api-lint to verify... Closed
Sprint: DevOps Sprint 131
Development Team: FOLIO DevOps

 Description   

We have been using AMF (AML Modeling Framework) v4 for our api-lint. This major version change to v5 now has a couple of patch releases, so it is time to upgrade our use of its amf-client-js.

Our JavaScript will need a complete re-write. The client is now much more easily configured. Access to the results of parsing and validation can now be handled separately. See documentation.



 Comments   
Comment by David Crossley [ 13/Jan/22 ]

The upgrade to AMF v5 was successfully completed.

Tested with in-development GitHub Workflow at mod-notes FOLIO-3202 Closed .

Updated jenkins-pipeline-libs to configure buildMvn to enable new option 'apiWarnings'.

Rebuilt and redeployed the folio-tools/jenkins-slave-docker image to include this upgraded folio-tools/api-lint. Tested via mod-notes and mod-eusage-reports.

Still need to update docs at api-lint

 

Comment by David Crossley [ 17/Jan/22 ]

Done.

Generated at Thu Feb 08 23:27:41 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.