index bases clean up (dangling) about devpi

[devpi-bot]

Original comment by @hpk42

we need to think about how to keep indices relations consistent. Could you maybe jump on IRC to #devpi on irc.freenode.net?

[devpi-bot]

Original comment by @hpk42

Should index deletion be rejected when someone else inherits from it?

[devpi-bot]

Original comment by @lbrack

That's a good question. It does make sense to reject it if someone inherits from it (at least another user).

But then, the draw back is if I create myself a sandbox, someone sees it and uses it as base, then I would have to chase that person around.

So I am wondering if we could do the following:

I am thinking in the line of public, protected and private.

• public means that anyone can see it, and use it as a base
• protected means that everyone can see it but can not use it as a base
• private only the owner see this (maybe this is too much)

But again, we are adding complexity which might not be needed.

However I can see a scenario where Jane inherits from one of my index. I don't know she does, and delete my index, messing her environment.

Even worst, we have the GTI prod index, and someone, by accident deletes it. Ouch.

[devpi-bot]

Original comment by @hpk42

What about preventing deletion of an index that is non-volatile? Volatile so far means that you can overwrite releases and release files on upload but we can extend the meaning to make an index non-volatile. a Prod index would be non-volatile. I just switched even hpk/dev to non-volatile.

[devpi-bot]

Original comment by @lbrack

Yup. It makes a lot of sense. A dev index is by definition something that is subject to flux.

so basically if an index is non-volatile and is a base to another index, it can't be deleted. Obviously could change from non-volatile to volatile but at least there is some warning.

[devpi-bot]

Original comment by @lbrack

One other thing to keep in mind. Deleting a user that has a non-volatile index which is used by someone else should be forbidden.

I will add a test case as a reminder