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
The only way to install aws-creds right now is to manually build a binary.
It'd be much nicer to have releases with pre-built binaries using a script that looks something like this:
#!/bin/bash# Need to use an older version of go for this releaseexport PATH=/usr/local/opt/[email protected]/bin:$PATH# Only supporting amd64 for nowexport GOARCH=amd64
# Hard-coding version, could derive from tagexport VERSION=v1.0.6
# Build for all major platformsforosin$(echo darwin windows linux);do# Set the OS for this buildexport GOOS=$os# Set the binary nameexport AWS_CREDS_BIN=aws-creds_${VERSION}_${GOOS}_${GOARCH}# Debugging outputecho"Building ${AWS_CREDS_BIN}"# Build the binary
go build \
-o bin/${AWS_CREDS_BIN} \
-ldflags "-s -w -X github.com/lob/aws-creds/cmd.version=${VERSION}";done# Build shasum fileecho"Building checksums file"pushd bin
shasum -a 256 aws-creds_${VERSION}_*> aws-creds_$VERSION.sha256sum
popdecho"Done"
A few problems with this are that MacOS doesn't like this at all and in fact it bars users from running binaries downloaded form GitHub built this way.
Figure out how to successfully build valid MacOS/Linux/Windows binaries.
Document how to build the release artifacts.
Add the release artifact builder to the repo.
Automate build + release steps.
The text was updated successfully, but these errors were encountered:
The only way to install aws-creds right now is to manually build a binary.
It'd be much nicer to have releases with pre-built binaries using a script that looks something like this:
A few problems with this are that MacOS doesn't like this at all and in fact it bars users from running binaries downloaded form GitHub built this way.
The text was updated successfully, but these errors were encountered: