Add command for removing libraries or releases #73
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These methods allow for removal of libraries and releases from the database.
This can be used for recovery in the event something goes wrong while in the middle of a operation that modified the production files content.
Previously, the tool's command line interface was only ever intended to provide the "sync" functionality so a single "all" integration test file was reasonable. Now that additional distinct command line functionality is planned, it will be better to separate the integration tests into multiple files to make it easier for the developer to navigate the code.
This will make writing tests easier and avoid code duplication.
Once a library submission is accepted, the registration and releases is stored in the library database. This means that a library release or library will remain in Library Manager even after the removal of a tag or repository by the library maintainer, or the removal of the library's registration from the registry. A library release or library removal requires direct action by a maintainer. This procedure will be facilitated by adding the capability to the engine tool's command line interface in the form of the new `remove` subcommand. It can be used to remove specific releases: ``` libraries-repository-engine remove LIBRARY_NAME@VERSION... ``` or libraries entirely: ``` libraries-repository-engine remove LIBRARY_NAME... ```
Rather than maintaining duplicated command line interface description in the readme, it is better to direct the user to run the `help` command, which will always provide the complete current documentation.
silvanocerza
approved these changes
Aug 25, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Once a library submission is accepted, the registration and releases is stored in the library database. This means that
a library release or library will remain in Library Manager even after the removal of a tag or repository by the library
maintainer, or the removal of the library's registration from the registry.
A library release or library removal requires direct action by a maintainer. This procedure will be facilitated by adding
the capability to the engine tool's command line interface in the form of the new
removesubcommand.It can be used to remove specific releases:
or libraries entirely: