-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ygot in an OCI image? #770
Comments
This sounds good to me, we already have a couple packages being released: https:/orgs/openconfig/packages. @robshakir any comments? |
@wenovus yes, I plan to follow the steps that were used in openconfig/gnmic project when it comes to releasing OCI artifacts. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: