Skip to content
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.

As a user, I want the registry loader tools to continue after the ingestion of a product fails #253

Closed
jordanpadams opened this issue Feb 15, 2022 · 0 comments
Closed

As a user, I want the registry loader tools to continue after the ingestion of a product fails #253

jordanpadams opened this issue Feb 15, 2022 · 0 comments
Assignees
@tdddblog @jordanpadams
Labels
B12.1 p.should-have requirement sprint-backlog

Comments

@jordanpadams
Copy link
Contributor

jordanpadams commented Feb 15, 2022 •
edited
Loading

💪 Motivation

...so that I can ingest large data sets, and go back and fix the issues afterwards.

📖 Additional Details

⚖️ Acceptance Criteria

Given a metadata label that contains some sort of metadata that is invalid (e.g. String where an integer should be)
When I perform a harvest and registy-mgr execution to ingest the data
Then I expect an ERROR message to be thrown, the product to not be ingested, but harvest/registry-mgr continuing ingesting the data

⚙️ Engineering Details
@jordanpadams jordanpadams self-assigned this Feb 15, 2022
@jordanpadams jordanpadams changed the title As a user, I want to registry ingestion to continue after the ingestion of a product fails As a user, I want the registry loader tools to continue after the ingestion of a product fails Feb 24, 2022
This was referenced Mar 30, 2022
Merged
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@tdddblog tdddblog

@jordanpadams jordanpadams

Labels
B12.1 p.should-have requirement sprint-backlog
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tdddblog @jordanpadams @tloubrieu-jpl