summaryrefslogtreecommitdiff
path: root/puppet/modules/site_stunnel/manifests
diff options
context:
space:
mode:
authorMicah Anderson <micah@riseup.net>2013-03-14 13:58:06 -0400
committerMicah Anderson <micah@riseup.net>2013-03-14 18:40:19 -0400
commitd4b45da9a521a6faf17f9ba7742bcee897a503cc (patch)
tree6b3883ac534a3b15737c545d7ccd5ab2b943946f /puppet/modules/site_stunnel/manifests
parent3c5c31e74954ebb7a55c9455809ea55375f273d5 (diff)
remove apache ssl proxy in preparation of replacing it with a stunnel setup
This presents us with an interesting problem of deprecation. We need to manage the removal of something that we previously installed in any released code. How long we carry the puppet code that removes raises some interesting questions: do we require that someone who deployed version 1 (where the apache ssl proxy was deployed) of the platform upgrade first to version 2 (where we remove the apache ssl proxy) before they upgrade to version 3 (where the apache ssl proxy removal is no longer present) -- or do we allow people to skip versions?
Diffstat (limited to 'puppet/modules/site_stunnel/manifests')
0 files changed, 0 insertions, 0 deletions