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
When using a context or any command with a custom CA via --certificate-path it seems to not be respected. I tested with zed v0.10.1 but I think it also appears in the latest version.
E.g. running zed schema read --log-level trace fails with:
When using a context or any command with a custom CA via
--certificate-path
it seems to not be respected. I tested with zed v0.10.1 but I think it also appears in the latest version.E.g. running
zed schema read --log-level trace
fails with:Even setting
--certificate-path
directly on the call does not change this.I could trace the issue back to
zed/internal/storage/config.go
Line 51 in 5520b40
I think one should carry over the
CACert
field from theCurrentToken
response. If that's also your understanding I can open a PR.The text was updated successfully, but these errors were encountered: