Draft: Change description and roles name (!8241) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

The aim of this MR is to correct a small mistakes into grafana roles definition, update description for grafanaadmin and the name of the roles into helm chart values.

Initial roles definitions seems to be wrong because defining:

    roles:
      grafanaviewer-role:
        description: "Viewer role for Grafana"

The role manifest will be:

# Source: keycloak-user-management/templates/roles.yaml
apiVersion: role.keycloak.m.crossplane.io/v1alpha1
kind: Role
metadata:
  name: grafanaviewer-role
  namespace: sylva-system
spec:
  forProvider:
    realmId: "sylva"
    name: grafanaviewer-role <= wrong substitution comparing with the role expected by grafana (  grafanaviewer) 
    description: "Viewer role for Grafana"
  providerConfigRef:
    name: keycloak-provider-config
    kind: ProviderConfig
  managementPolicies:
    - "*"

Credits to @cisaroiu whom noticed this small mistake.

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 Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

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 Jun 16, 2026 by Bogdan Antohe

Draft: Change description and roles name

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports