[FOLIO-1501] folio-ansible: data load error parsing Created: 15/Sep/18  Updated: 15/Jan/19

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

Type: Bug Priority: P3
Reporter: Wayne Schneider Assignee: Wayne Schneider
Resolution: Unresolved Votes: 0
Labels: ci
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-1500 Environment builds fail due to invali... Closed
Sprint:
Development Team: Core: Platform

 Description   

Error reporting for data loading is not consistent among FOLIO endpoints. The Ansible tasks that load data need to be able to distinguish between a duplicate record (which should not be an error in an idempotent load script) and malformed data, both of which may result in a 422 (unprocessable entity) error. Some endpoints will report a 400 for a duplicate record. The current module-sample-data task reports "changed" if the endpoint reports a 2XX and "unchanged" if the endpoint reports a 400 or 422. This is not granular enough to catch mismatches between the sample data and the schema.

For performance reasons, it is not practical to check for the existence of every sample record before loading, so some level of error message parsing should be added to the role.


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