On 3/13/16 4:51 AM, Pranav Sharma wrote:
> I believe currently the subprojects are not allowed to actually be deleted
> from the neighborhood. Because when I try to do so, some tests are failing.
> Like,
> 
> allura.tests.functional.test_admin.TestProjectAdmin.test_project_delete_not_allowed
> 
> with the error code as
> 
> AppError: Bad response: 404 Not Found (not 200 OK or 3xx redirect for
> http://localhost/p/test/sub-no-del/admin/overview)
> 

On IRC a few days ago you mentioned you had resolved the first problem, that
means this test, I'm assuming.  Let us know if not.

> So, if that's the case, and the subprojects are not allowed to be deleted,
> then their mount points should not be allowed to be reassigned, because
> that would just create dangling subprojects into memory.
> 
> And that would create the error at last that the urls/ mount points
> assigned to new tools that were previously pointing to subprojects continue
> to do so. So, either the subprojects should be deleted permanently, or the
> mount points once used should not be allowed to be assigned by the user.

The goal for this ticket is to allow users to use a mount point, after deleting
a subproject.  Users will sometimes try a subproject and then decide they don't
want it and try to create a repo with that name instead.  They should be able to
do that.  I think it would be okay for the subproject to be dangling in memory,
and not necessarily accessible.



-- 
Dave Brondsema : [email protected]
http://www.brondsema.net : personal
http://www.splike.com : programming
              <><

Reply via email to