[Feature] Expose gokart version #2
Comments
kuritka
added a commit
to k8gb-io/k8gb
that referenced
this issue
Sep 7, 2021
related to #600 I considered using a go-kart action. Unfortunately it is not yet mature enough to use it ([1](kitabisa/gokart-action#2), [2](kitabisa/gokart-action#1)). During the processing `build.yaml` I run gokart the same way as for example golic. Signed-off-by: kuritka <[email protected]>
kuritka
added a commit
to k8gb-io/k8gb
that referenced
this issue
Sep 7, 2021
closes #600 I considered using a go-kart action. Unfortunately it is not yet mature enough to use it ([[1]](kitabisa/gokart-action#2), [[2]](kitabisa/gokart-action#1)). During the processing `build.yaml` I run gokart the same way as for example golic. Signed-off-by: kuritka <[email protected]>
|
If we just expose what version of GoKart using, that's fine. But I don't think it's possible to "specify the version of the gokart as action argument", because I believe if it's dynamic, then the action inputs should be too. |
kuritka
added a commit
to k8gb-io/k8gb
that referenced
this issue
Sep 10, 2021
closes #600 I considered using a go-kart action. Unfortunately it is not yet mature enough to use it ([[1]](kitabisa/gokart-action#2), [[2]](kitabisa/gokart-action#1)). During the processing `build.yaml` I run gokart the same way as for example golic. Signed-off-by: kuritka <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice if I could explicitly specify the version of the gokart as action argument.
The reason is that locally I can use a different version of the gokart than in action. This would create an inconsistency where the action gokart would return different results than the local scan.
WDYT?
The text was updated successfully, but these errors were encountered: