[katello-devel] Demotions and deletions - solution

[Lukas Zapletal]

After chat with Brad, we came to conclusion there are two good solution:

A) Do not let user to delete a repo that has promoted content

A) Do not allow a user to delete a repo that has been promoted... in
this case, give the user a strong warning that it must first be deleted
from A,B,C environments

B) Allow users to delete repos. When creating a repo, first check if the
name is already used in any environment. If so, do not let user to
create the repo telling him/her he need to choose a different one or to
delete all repositories with that name using changesets.

C) B + auto create deletion changeset when deleting repos. This is what
Mike recommend I guess plus with the B check. (*)

(*) The question is do we want to auto create for ALL possible
environment paths? That could be lots of changesets. Maybe to do this
optional, or maybe even a separate command/action. Something like
"recursive promote".

LZ


On Tue, Aug 28, 2012 at 12:29:47PM +0200, Lukas Zapletal wrote:
> Hey,
> 
> stumbled upon a bug (https://bugzilla.redhat.com/show_bug.cgi?id=835875)
> that prevents you from creating a repository with a same name that has
> been deleted (but promoted).
> 
> Now the question - we now do support demotions (those promotions
> opposite - not sure about wording). Therefore I guess the proper
> solution would be to check if the repository (*) was already promoted.
> If so, Katello will refuse to delete the object asking user to do the
> demotion.
> 
> Opinions?
> 
> (*) this should apply to anything that is promotable:
> 
> - product
> - repo
> - template
> - package
> - erratum
> - distribution
> 
> -- 
> Later,
> 
>  Lukas "lzap" Zapletal
>  #katello #systemengine
> 
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel

-- 
Later,

 Lukas "lzap" Zapletal
 #katello #systemengine