Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As a user I want to delete whole bundles at once #52

Open
mdrum opened this issue Aug 15, 2022 · 4 comments
Open

As a user I want to delete whole bundles at once #52

mdrum opened this issue Aug 15, 2022 · 4 comments
Assignees
Labels
icebox p.should-have requirement the current issue is a requirement

Comments

@mdrum
Copy link

mdrum commented Aug 15, 2022

💪 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: NASA-PDS/registry#98

@jordanpadams
Copy link
Member

@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

@jordanpadams jordanpadams removed their assignment Aug 16, 2022
@mdrum
Copy link
Author

mdrum commented Aug 16, 2022

Yea @jordanpadams that only works if you harvested exactly one bundle per job, which is often not how harvest configs are built

@tloubrieu-jpl
Copy link
Member

Dan Scholes need that as well.

@tloubrieu-jpl
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
icebox p.should-have requirement the current issue is a requirement
Projects
Status: ToDo
Development

No branches or pull requests

4 participants