What are the best practices for stop hook handling?

[Rye Terrell]

> Do you have a real world example at hand?

No, why?

On Thu, Oct 20, 2016 at 2:26 PM, Free Ekanayaka <
free.ekanayaka at canonical.com> wrote:

> On 20 October 2016 at 16:09, Rye Terrell <rye.terrell at canonical.com>
> wrote:
>
>> > Subordinate charms only make sense when collocated. And I would argue that
>> subordinates are extremely common, at least in production environments.
>>
>> > In this context clean up is very important because it's not unusual
>> for operators to switch technologies. For example replace telegraf with node-exporter
>> or collectd.
>>
>> With that in mind, I'd like to reiterate one of my original questions:
>> how do we handle cleanup in the case where two or more colocated charms
>> have the same dependencies? In the case of background services, do we not
>> stop & disable them? Do we stop & disable them and expect the remaining
>> charms to repair the situation?
>>
>
> Do you have a real world example at hand?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20161020/ebaea46a/attachment.html>