Ivan Ka
What the expected behaviour is in your opinion? Looks like 0.5.2 has some undocumented fix
I have no time to validate yet. But worth to double check the behaviour of the camelcase function. If test became a Test is not a camelCase but a PascalCase....
Ok found out why the behavior differs in never version. The fix exists in dependency https://github.com/huandu/xstrings which is an indirect dependency to sprig and helm
Agree it's a bug. As there is a version mistmatch in between Helm and Helm unittest
The helm-unit test's release cycle is unpredictable and lacks a fixed schedule. If you encounter issues, you're welcome to submit a pull request that reverts to a previous version with...
Worth to write a unit and end-2-end test to cover this behavior. Dependency is update - sprig https://github.com/Masterminds/sprig/blob/e708470d529a10ac1a3f02ab6fdd339b65958372/go.mod#L10 - helm https://github.com/helm/helm/blob/3a3e3846ca9c929a6966583b461181e70f19bc13/go.mod#L9C2-L9C33 dependency bump for helm https://github.com/helm-unittest/helm-unittest/pull/411 related as well. So...
I think I found one of the bottlenecks /lifecycle frozen /assign
It's a bit problematic to support previous versions. I do get that the issue is open a while back. Is this still happening with the latest external-dns?
Hi @gjtempleton and @drmorr0 . This seems like a chunk of work. What is the process to swap SDK? Is this sounds reasonable 1. First pull request. Create aws-sdk-go-v2 folder...