Go to file
Thomas Lamprecht b1e879ecae api acme: use the same plugin config for an order
re-loading it always would mean that we could potentially switch the
config to something completely different, and the mix of the previous
and the old could result in total bogus actions.

Better to use the same one for one full order, even if it may get
"outdated" it was still valid in the past and most important
coherent.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2020-05-03 18:46:12 +02:00
aplinfo update shipped appliance index for PMG 6.2 2020-04-28 11:03:28 +02:00
bin cert renew: note reason why renewal due to long lifetime is done 2020-04-27 18:28:59 +02:00
configs buildsys: fixup: fully remove pve-apt-hook mentionings 2019-06-28 10:57:03 +02:00
debian d/control: bump versioned dependency on pve-cluster 2020-05-03 14:10:17 +02:00
network-hooks ifupdown1: bridgevlan: add bridge-vids list support 2020-01-11 17:22:46 +01:00
PVE api acme: use the same plugin config for an order 2020-05-03 18:46:12 +02:00
services pvesr service: order after pve-cluster 2019-11-28 10:54:12 +01:00
test test: s/expeted/expected 2020-04-10 10:34:13 +02:00
www sdn: remove reverts buttons 2020-05-03 16:36:46 +02:00
.gitignore Extend the .gitignore(s) 2018-05-04 14:50:04 +02:00
defines.mk fix #844: allow to pre-delay start-all-marked guests on boot 2019-11-20 20:20:58 +01:00
Makefile pvecfg: adapt version and release semantic 2019-05-26 16:11:43 +02:00
spice-example-sh doc: spice-example-sh: support special characters in passwords 2017-10-05 13:57:27 +02:00
vzdump-hook-script.pl vzdump: hook script example: s/openvz/lxc/ 2018-11-05 10:33:34 +01:00