| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Change-Id: Ia5f35977b3dad08c10256f0281ab36ffb230c9fd
|
|
cipher used as well as the client and issuer CommonName into the "Received:" header
Also, clean up the parameters to standardize them
Change-Id: Ib6be27f0f93e0a9e20fbdffa1d42220a25fc8ed4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
site_config::x509::client_ca::key for client_ca deployment (#3917)
|
|
|
|
|
|
|
|
|
|
|
|
leap_cli).
|
|
|
|
(fixing #3384)
node name and dns fqdn could be different
Also note that on local deploys that warning from #3384 will continue to exist (because of dns)
|
|
on the same node (requires latest leap_cli)
|
|
|
|
(#3782)
in commit 338833, we established a relationship between all
resources that have a leap_service tag, that are called in site.pp.
But we had some resources as default on every node in site.pp
(apt::update, Package { require => Exec['apt_updated'] },
site_config::slow and stdlib), that were still lacking any
relationship to the leap_service tag.
By moving them into default.pp they automatically are executed
before resources with a leap_service tag.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#3838)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
shorewall is setup before the service is setup. This is necessary due to the strict initial firewall that stops various service setup operations from happening, but is relaxed once shorewall is setup properly (#3782)
Change-Id: Ia9640c4118aa0053cdb99e7bc11860fed5527501
|
|
|
|
|
|
|
|
|
|
during main puppetrun, even before shorewall is configured completly
|
|
Change-Id: Ia236eb5b7609d9f96970230fce4d0051d832e3cb
|
|
|
|
|
|
the main interface we use (#2399, #2401)
|
|
Change-Id: I33292b9eb2a5553ac296857c99fdaf350ed52542
|
|
|
|
(https://leap.se/code/issues/3861)
|
|
|
|
Change-Id: I593602ff9d3486dee39227673147e137045c55c5
|
|
|
