5423d6711b
The webhook from portieris is configured to fail if the app cannot
respond, as a safety measure. However, during upgrades, this causes
issues when portieris itself and the other apps are updated.
This change modifies the lifecycle from portieris to disable the
webhook upon a manual update. This is done by change the application's
overrides, that will be used to recreate the webhook upon apply.
It also creates another lifecycle action to remove the changes once
the app is updated.
Test plan:
PASS: Performed stx 8 -> stx 10 upgrade activation and portieris w/ no
overrides. Observed that after portieris update, the overrides are
changed and the webhook is disabled once the app is upgraded.
Observed that after completing the update, the overrides are
removed and the webhook is reconfigured to default value.
PASS: Performed stx 8 -> stx 10 upgrade activation and portieris w/
overrides for the webhook. Observed that after portieris update,
the overrides are changed and the webhook is disabled once the
app is upgraded. Observed that after completing the update, the
overrides are changed back to previous values and the webhook is
reconfigured to this values.
PASS: Deployed stx 10 and applied portieris. Tested basic functionality
w/ policy restrictive to unsigned images. Deployed two pods with
busybox image, one signed (allowed) and the other unsigned
(disallowed).
Story: 2010676
Task: 51215
Change-Id: Ie5012a205b51f2db2e5f3e75ed31a7cf1ccdd83d
Signed-off-by: Marcelo de Castro Loebens <Marcelo.DeCastroLoebens@windriver.com>