Comment 30 for bug 2012689

We had discussion around adding `snap refresh --hold`, but felt that keeping the ability to force changes to a channel in times like these was paramount. The general expectation is that a `snap refresh` should never result in downtime for an active service (and if it does, it should be fixable within the snap for most cases). I am still open to the option, but I worry that we would not have enough visibility to advertise critical updates to EKS users with long running clusters.

The suggested bootstrap.sh fix seems perfectly reasonable and I think we could approach that in the near term. I'll make sure it gets prioritized soon.