Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
New Keycloak Operator KeycloakSpec CRD ingress disabled boolean is incorrect
See original GitHub issueDescribe the bug
The generated YAML for the operator has disableDefaultIngress as the property, but the way the code is written, it is looking for defaultIngressDisabled which means you can never use this property in the resource.
Version
18.0.0
Expected behavior
The YAML should mirror the code and have defaultIngressDisabled as the property name.
Actual behavior
The YAML lists disableDefaultIngress as the property name
How to Reproduce?
Create a Keycloak resource with either property name and it will fail for one of two reasons.
Anything else?
No response
Issue Analytics
- State:
- Created a year ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
yeah, would be good to have a minor release with that feature, currently only nightly works well and this is really a must-have option
Well that’s timing 😃 Sorry for the bother then and thank for the hard work.