Joseda Rios
Joseda Rios
Any update on this? I am facing the same issues cross-compiling this project using Bazel: ``` ERROR: WORKDIRvendor/github.com/goccy/go-graphviz/internal/ccall/BUILD.bazel:3:11: GoCompilePkg vendor/github.com/goccy/go-graphviz/internal/ccall/ccall.a failed: (Exit 1): builder failed: error executing command bazel-out/darwin-opt-exec-2B5CBBC6/bin/external/go_sdk/builder compilepkg...
This is fixed at #3299!
+1 to this feature request
> The reason we left this option to false was so we do not change previous behavior of the tool. But there are other methods to communicate behavioral changes such...
I am probably missing more details because I foresee problems: - What if the target registry is not an OCI-compliant registry? I do understand container images and chart helm templates...
I understand. Then I would just make sure we add some breaking changes notes to the release.
Since the configuration is not meant to be serialized and transferred between applications, I am OK relying on viper only.
Hello! Currently, the charts-syncer tool is not expected to work as a non-root. We will look into it in future versions.
Hello @LP0101! I am glad you discovered this bug. Sadly, we don't plan to add support for multiple source chart repositories at the moment. However, we will be happy to...
Do you expect to make this happen anytime soon? It would be great!