[FOLIO-3553] Upgrade amf-client-js to v5.2.0 for api-lint Created: 08/Aug/22  Updated: 26/Oct/22  Resolved: 26/Oct/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-3560 Erroneous api-lint validation for mod... Closed
relates to FOLIO-2893 Create folio-tools/api-lint to verify... Closed
Sprint: DevOps Sprint 146, DevOps Sprint 149, DevOps Sprint 150, DevOps Sprint 151
Development Team: FOLIO DevOps
RCA Group: TBD

 Description   

We use AMF (AML Modeling Framework) v5.0.10 for our api-lint.

Upgrade our api-lint and verify against the current set of RAML/OAS API descriptions.

Update 2022-09-22: Awaiting AMF version v5.2.0 (due around October 19) which has a fix for the bug revealed at FOLIO-3560 Closed .



 Comments   
Comment by David Crossley [ 15/Aug/22 ]

Done via folio-tools/pull/248

So is ready for local use.

But not yet deployed to Jenkins CI.

Comment by David Crossley [ 30/Aug/22 ]

An issue was discovered that affected only mod-patron and edge-patron (see FOLIO-3560 Closed ). The issue remains in the next AMF v5.0.12 version.

So reverted this upgrade. Will await a future AMF version.

Comment by David Crossley [ 22/Sep/22 ]

Awaiting AMF version v5.2.0 (due around October 19) which has a fix for the bug revealed at FOLIO-3560 Closed .

Comment by David Crossley [ 26/Oct/22 ]

Done. Upgraded api-lint and api-doc to use the current amf-client-js v5.2.0 and deployed to Jenkins via FOLIO-3573 Closed .

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