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
Device and OS: N/A
App version: 0.9.0
Kubernetes distro being used: N/A
Other:
uds cli used to not care about the case for the names of bundle overrides. At some point this behavior changed such that an override defined in lowercase would not have the respective value in uds-config.yaml assigned to it
variable in uds-config.yaml gets read in and passed through to the helm chart
Actual Result
It wont happen. Note: if a default value is defined, it propogate to the vlaues file appropriately even if the name is lowercase. This issue is specifically that the value is getting dropped between the bundle-config and the actual overriding of the helm chart.
Visual Proof (screenshots, videos, text, etc)
Confirmed with Darcy this morning
Severity/Priority
Additional Context
Add any other context or screenshots about the technical debt here.
The text was updated successfully, but these errors were encountered:
Environment
Device and OS: N/A
App version: 0.9.0
Kubernetes distro being used: N/A
Other:
uds cli used to not care about the case for the names of bundle overrides. At some point this behavior changed such that an override defined in lowercase would not have the respective value in uds-config.yaml assigned to it
Steps to reproduce
To reproduce, take the bundle overrides test case
uds-cli/src/test/bundles/07-helm-overrides/uds-bundle.yaml
Line 42 in 1bc39aa
SECURITY_CTX
tosecurity_ctx
.Expected result
variable in uds-config.yaml gets read in and passed through to the helm chart
Actual Result
It wont happen. Note: if a default value is defined, it propogate to the vlaues file appropriately even if the name is lowercase. This issue is specifically that the value is getting dropped between the bundle-config and the actual overriding of the helm chart.
Visual Proof (screenshots, videos, text, etc)
Confirmed with Darcy this morning
Severity/Priority
Additional Context
Add any other context or screenshots about the technical debt here.
The text was updated successfully, but these errors were encountered: