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
Hi @wenovus@robshakir,
I use ygot to generate structs that I later on publish as a go package. My workflows are run in CI and currently I pin the ygot version due to gnmi 0.7 dependencies.
Ygot installation is now only possible with go install command, and I wonder if you agree that it'd be cool to have an automated pipeline that packages the binary when a new semver tag is pushed in a repo and publishes the OCI image using already provided ghcr.io/openconfig registry?
This will open the doors to less involved generation pipelines. If the idea sounds good to you, I can contribute a GH actions workflow that leverages goreleaser to build the binary and package/publish the OCI artifact.
The text was updated successfully, but these errors were encountered:
@wenovus yes, I plan to follow the steps that were used in openconfig/gnmic project when it comes to releasing OCI artifacts.
Will wait for @robshakir to comment and if/when GO is given I can look into it
Hi @wenovus @robshakir,
I use ygot to generate structs that I later on publish as a go package. My workflows are run in CI and currently I pin the ygot version due to gnmi 0.7 dependencies.
Ygot installation is now only possible with
go install
command, and I wonder if you agree that it'd be cool to have an automated pipeline that packages the binary when a new semver tag is pushed in a repo and publishes the OCI image using already provided ghcr.io/openconfig registry?This will open the doors to less involved generation pipelines. If the idea sounds good to you, I can contribute a GH actions workflow that leverages goreleaser to build the binary and package/publish the OCI artifact.
The text was updated successfully, but these errors were encountered: