On 8 June 2016 at 21:23, Tom McKay <[email protected]> wrote: > To me, as a user, if I delete an org (or location) I'd simply want the > foreman resources to be unassociated from it. It may be the case, for > example, that a resource like a provisioning template is shared among > multiple orgs. A host is different, I know, in that it can belong to only > one org but I would still lean towards consistency by throwing it into the > bucket of unassociated hosts. >
I think that has to be the choice - whilst you *could* go to the edit location page and unassign *every signle resource* from a bazillion tabs, it very tedious, and ends up with the same result anyway. So long as we document the behaviour clearly, then I think it's fine to just drop associations -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
