You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How does one go about having Puppet manage squid's cache_dir fully when it is to be on a separate filesystem. This module has squid::cache_dir which will create what will be the mount point, but if I want to have Puppet manage that mount I get into ordering problems. I cannot declare my own mount to occur before the squid class because the mount point may not exist yet or if I ensure it does, I'll have a duplicate declaration for it. If I declare the mount to occur after squid the mount point will exist so this can succeed but then it must notify => Class[squid`] (I believe) to actually start using it. This likely means restarting squid which seems sub-optimal. I guess that would only occur once during the initial setup so it's not terrible or is there a better way yet?
The text was updated successfully, but these errors were encountered:
ralfbosz
added a commit
to ralfbosz/puppet-squid
that referenced
this issue
Dec 28, 2018
How does one go about having Puppet manage squid's cache_dir fully when it is to be on a separate filesystem. This module has
squid::cache_dir
which will create what will be the mount point, but if I want to have Puppet manage that mount I get into ordering problems. I cannot declare my ownmount
to occur before the squid class because the mount point may not exist yet or if I ensure it does, I'll have a duplicate declaration for it. If I declare themount
to occur aftersquid
the mount point will exist so this can succeed but then it mustnotify => Class[
squid`] (I believe) to actually start using it. This likely means restarting squid which seems sub-optimal. I guess that would only occur once during the initial setup so it's not terrible or is there a better way yet?The text was updated successfully, but these errors were encountered: