You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pkosiec
changed the title
Wrong configuration merging when using existingCommunicationsSecretName
Wrong source bindings when using existingCommunicationsSecretNameSep 22, 2023
Description
Source bindings are not properly set when using
existingCommunicationsSecretName
.Expected behavior
When using
existingCommunicationsSecretName
,runtime-config
doesn't have source bindings from the secret, but from default configuration instead.Actual behavior
Steps to reproduce
Ok, I could reproduce that with existingCommunicationsSecretName :
Where /tmp/comm_config.yaml is:
And then I ran
where
The text was updated successfully, but these errors were encountered: