30a450183a
Add OIDC configuration logic to the lifecycle, aligned with the
bootstrap setup but designed not to overlap with it. This mechanism
runs during platform or application updates, not during system
installations, ensuring no conflict with the bootstrap process.
The lifecycle now validates the existing OIDC configuration before
applying the oidc-auth-apps.
Behavior:
- If a complete OIDC configuration is detected, the application is
applied without any additional actions.
- If no OIDC configuration is found but related service parameters
exist, the lifecycle performs the required additional configuration
before applying OIDC.
- If a partial or incomplete OIDC configuration is detected, the
apply operation fails.
Test Plan:
PASS: build-pkgs
PASS: build-image
PASS: Platform upgrade and rollback validated on:
- AIO-SX (IPv4)
- AIO-SX (IPv6)
- AIO-DX
- Distributed Cloud
Expected behavior:
- During upgrade, OIDC is applied using either the existing
configuration or the default configuration, as appropriate.
- After rollback, OIDC returns to the same state it was in before
the upgrade process began.
Story: 2011535
Task: 53479
Depends-on: https://review.opendev.org/c/starlingx/update/+/973191
Change-Id: Ia32a6a201e9392b57a64bb8f9e104d46a054244c
Signed-off-by: Eduardo Almeida <Eduardo.AlmeidadosSantos@windriver.com>