Primary color (dark mode) is no valid Hex color value (POLICY-391dG)
I come with a very weird bug 
As you might know, we configure Zitadel mostly as code.
So did we the First and Default Instance. Only did I make one tiny mistake:
Before
After
Now, so far so good, the change is also rolled out (see Argo screenshot [white bg]). The deployment was also properly restarted by the change detection and twice by me but still the change does not get reflected, the UI stays unreadably wrong and if you click Branding this error shows.
Also, sadly, saving from the UI the new color does not have any effect.
Do you happen to know where I lack a piece to fix? Is that color stored wrongly into the DB at all?
Due to #enterpriseDebt we are on v2.70.13 still but migrations have started
TQ all
As you might know, we configure Zitadel mostly as code.
So did we the First and Default Instance. Only did I make one tiny mistake:
Before
After
Now, so far so good, the change is also rolled out (see Argo screenshot [white bg]). The deployment was also properly restarted by the change detection and twice by me but still the change does not get reflected, the UI stays unreadably wrong and if you click Branding this error shows.
Also, sadly, saving from the UI the new color does not have any effect.
Do you happen to know where I lack a piece to fix? Is that color stored wrongly into the DB at all?
Due to #enterpriseDebt we are on v2.70.13 still but migrations have started
TQ all
