Age | Commit message (Collapse) | Author |
|
Change-Id: I772c3b6e489e3c1848c45c6bcaa240324fc88928
|
|
|
|
Change-Id: I7675dbaba4d896a62dab9fcf4817092ea69f1298
|
|
It turns out that in some corner-cases, the script is not called:
(1) start the deploy, create files in /var/lib/puppet/stunnel4/config
(2) halt puppet before apply finishes
(3) re-run deploy
in this scenario, next time you run deploy, refresh_stunnel will never
get called to populate /etc/stunnel, because the files in
/var/lib/puppet/stunnel4/config haven't changed.
This problem can be really confusing when it happens.
To fix this, we just run refresh_stunnel every, it is pretty fast and
the script has more complete logic for what to do than puppet, which has
only an asymmetrical view on the situation.
Change-Id: I9e5fad1d081c2fe07f3ac8f07cfb87d86b88f7c9
|
|
|
|
the service has been started (#6495)
Change-Id: Id48fedb5731117b68b7386c4ce22516333d94081
|
|
Change-Id: Ia236eb5b7609d9f96970230fce4d0051d832e3cb
|
|
Change-Id: I33292b9eb2a5553ac296857c99fdaf350ed52542
|
|
(https://leap.se/code/issues/3861)
|
|
|
|
Change-Id: I9ed218d9353c05b34d34c363a6a3f10d54b3a60a
|
|
|
|
|
|
parameterized classes and qualified variables
update our stunnel class instantiation to be parameterized
|
|
|