Closed lsoica closed 1 year ago
did you try adding the scheme prefix oci://
to your registry
URI?
Yes, here's what I get with oci://
Error: Command failed with exit code 1: helm registry login --username <redacted> --password-stdin oci:
time="2023-03-14T11:49:14Z" level=info msg="Error logging in to endpoint, trying next endpoint" error="Get /"https://oci/v2//": dial tcp: lookup oci on 10.43.0.10:53: server misbehaving"
I think there's a split there on ':'
I was only able to make it work with helm v3.6.3
in the log it shows https
as protocol, I mean just specifying oci
protocol
I thought it's a fallback to http. Here's what I have in .releaserc:
"plugins": [
[
"semantic-release-helm3",
{
chartPath: './chart',
registry: 'oci://<fqdn>/<chart name>'
}
]
that looks correct, if this does not work, the only option is to downgrade helm I suppose
I have the same problem, any news ?
I think the right question is, @nflaig do you accept PRs?
@lsoica yeah for sure, contributions are always welcome, I am happy to review & release. I try to fix stuff myself if I can (see https://github.com/nflaig/semantic-release-helm/pull/12) but I really do not have that much time at the moment to work on this. I also do not use this plugin myself any longer and do not have good setup right now to test it properly.
In case someone want to implement a fix for this, if it is related to having different syntax based on helm version, there are helpers for this
might just add another branch like it is done here
Got this error:
with helm: