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
It would be useful to be able to verify the intended SHA of the release binaries in order that automated image build scripts can verify them. Would you consider publishing them along with binary artifacts?
One thing I did wonder is whether we could switch gomplate to using goreleaser, as it deals with lots of these release pipeline bits in a standardised fashion, including building .deb and .rpm packages? I'm happy to do this work if necessary.
The text was updated successfully, but these errors were encountered:
@jen20 Definitely agree about the SHAs - I've had that thought in the past, just haven't gotten around to it 😉.
I've been thinking about looking at goreleaser too. Let me have a look at it - it'd be a fairly big (potentially positive!) change to how gomplate is built/released.
It would be useful to be able to verify the intended SHA of the release binaries in order that automated image build scripts can verify them. Would you consider publishing them along with binary artifacts?
One thing I did wonder is whether we could switch
gomplate
to using goreleaser, as it deals with lots of these release pipeline bits in a standardised fashion, including building.deb
and.rpm
packages? I'm happy to do this work if necessary.The text was updated successfully, but these errors were encountered: