Open mdrum opened 1 year ago
@mdrum as a workaround, you may be able to run it based upon the package_id
. However, not entirely sure how that works with the harvest service
Yea @jordanpadams that only works if you harvested exactly one bundle per job, which is often not how harvest configs are built
Dan Scholes need that as well.
Sorry @mdrum @scholes-ds, we missed to have that completed for the build 13.1.
We will have that as high priority for next build.
💪 Motivation
...so that I can avoid being forced to run a delete command for every lidvid in a bundle
📖 Additional Details
If one harvests an initial bundle by directory that includes several other bundles/products, it becomes impossible to efficiently delete products using packageId. In this case, it would be nice if the delete-data command allowed a flag that followed the same logic as set-archive-status, which is that it follows references all the way down to the product level if the provided lidvid is for a bundle or collection.
⚖️ Acceptance Criteria
If I run
registry-manager delete-data -lidvid urn:nasa:pds:somelidvid
where that lidvid represents a bundle or collection, then registry manager will perform a delete for every primary product within that bundle or collection (including refs).⚙️ Engineering Details
Additional example here: https://github.com/NASA-PDS/registry/issues/98