Fix vault sso secret (!7334) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

After we merged !7288 (merged), multiple errors in hurl test related to sso were spotted and looking into vault secret for sso-account, the content was not the expected one, valuesFrom option does not pass the vault-startup-secret values to vault.

Vault secret sso-account content

{
  "login": {
    "valueFrom": {
      "secretKeyRef": {
        "key": "login",
        "name": "vault-startup-secret"
      }
    }
  },
  "password": {
    "valueFrom": {
      "secretKeyRef": {
        "key": "password",
        "name": "vault-startup-secret"
      }
    }
  }
}

   |
   | POST https://{{keycloak_url}}/realms/sylva/protocol/openid-connect/token
   | ...
11 | username: {{user_sso}}
   |             ^^^^^^^^ expression with value Object() can not be rendered

We get sso user and password via vault:

 GET https://{{vault_url}}/v1/secret/data/sso-account
X-Vault-Token: {{token}}
HTTP 200
[Captures]
password_sso: jsonpath "$.data.data.password"
user_sso:  jsonpath "$.data.data.login"

Looking into vault operator documentation I saw that we are able to add environment variables using envsConfig and using them into vault configuration. ( see: https://bank-vaults.dev/docs/operator/environment-variables/ & https://bank-vaults.dev/docs/operator/templating-configuration/#using-templates)

Test coverage

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment (i.e `real-bmh` for capm3 )

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Edited Mar 23, 2026 by Bogdan Antohe

Fix vault sso secret

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports