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
Add a generic end-point for deleting repository paths in the StoragesConfigurationController #1401
Labels
Comments
Open
6 tasks
Hi, if @adithyaChander is not working on this, can I pick this up? |
Open
6 tasks
Can I work on this? |
Go for it! :) |
10 tasks
mans4321
added a commit
to mans4321/strongbox
that referenced
this issue
Nov 12, 2019
…ConfigurationController strongbox#1401
mans4321
added a commit
to mans4321/strongbox
that referenced
this issue
Nov 12, 2019
…ConfigurationController strongbox#1401
10 tasks
mans4321
added a commit
to mans4321/strongbox
that referenced
this issue
Nov 20, 2019
…ConfigurationController strongbox#1401
mans4321
added a commit
to mans4321/strongbox
that referenced
this issue
Nov 25, 2019
…ConfigurationController strongbox#1401
mans4321
added a commit
to mans4321/strongbox
that referenced
this issue
Dec 7, 2019
…ConfigurationController strongbox#1401
is this issue still open? |
Can I work on this? |
@dreameral : This task is on hold. Perhaps you could look for another one? :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Task Description
We need to create end-points for moving repository paths. The code should be located in the
StoragesConfigurationController
class and a separate form class should be created so that it is able to handle theJSON
below. Be sure to check our How to write Spring Controllers guide to see how we return errors. There is some partial implementation of this in theMavenArtifactController
which could be useful to speed-up the development of this feature. The existing implementation should be refactored as much as possible and made generic enough that it works for all layout providers.Deleting a path in a storage/repository
Action:
Deletes recursively the content of
path
located under the definedstorageId
andrepositoryId
.Form validation:
The
force
field is used to determine if we should delete the files on the filesystem as well or not.Use the
BaseController#getSuccessfulResponseEntity
andBaseController#getFailedResponseEntity
(or if necessaryBaseController#getBadRequestResponseEntity
) to return the appropriate responses.Tasks
The following tasks will need to be carried out:
Task Relationships
This task relates to: #1399, #1400
Help
The text was updated successfully, but these errors were encountered: