It will be nice for users to have the ability to delete a garden. If the garden's DOI is one the user has in their data.json, this will both delete the garden locally and in the search index. If the garden has a registered DOI, the command should refuse to delete the garden. There should also be a hidden --force flag or similar that will delete the garden from the search index even if it isn't in the user's data.json. This will be useful for admins.
Assumptions:
1.
2.
Acceptance Criteria
Given I am a publisher, when I publish a test garden that I don't really want published, then I can garden-ai garden delete it.
It will be nice for users to have the ability to delete a garden. If the garden's DOI is one the user has in their data.json, this will both delete the garden locally and in the search index. If the garden has a registered DOI, the command should refuse to delete the garden. There should also be a hidden
--forceflag or similar that will delete the garden from the search index even if it isn't in the user's data.json. This will be useful for admins.Assumptions:
1. 2.
Acceptance Criteria
Given I am a publisher, when I publish a test garden that I don't really want published, then I can
garden-ai garden deleteit.