Aws-iam-authenticator: Add homebrew support

Created on 11 Jun 2018  ·  14Comments  ·  Source: kubernetes-sigs/aws-iam-authenticator

Then we could install it just like kops, kubectl etc. Copying a binary from an S3 bucket is not so cool 🙂

Most helpful comment

I think this would be a great idea. The build/release tool we're currently using supports publishing to a Homebrew tap, so this should be pretty easy to stand up.

All 14 comments

I think this would be a great idea. The build/release tool we're currently using supports publishing to a Homebrew tap, so this should be pretty easy to stand up.

Would be handy for ekctl too (https://github.com/weaveworks/eksctl/issues/43), although I'm not sure if cross-tap dependencies are supported... Any chance authenticator could be added to Homebrew core?

Do we have one for kubernetes-sig org? @errordeveloper this project is being moved under there eventually so that would be useful. It doesn't look like it, has that been brought up @spiffxp

We should talk about that being a long-term approach for eksctl as well…

@christopherhein I have just tried using goreleaser to make a homebrew tap for eksctl, but had no success due to https://github.com/goreleaser/goreleaser/issues/686.

Do we have one for kubernetes-sig org?

I doubt. All Kubernetes formulae are in homebrew-core, which is hard for a project in early stage, as you have to make a PR to bump the version for each release.

So as a method of packaging do you think for sig projects (and incubator separate topic) we could potentially get a repo for a tap? It seems like that would be a useful way for anyone to that makes sig owned projects; would still require a PR but at least we’d be a little more in control of it... might be a much bigger ask than I’m thinking

Perhaps we should get back to this topic after the project gets transferred
over.

On Mon, 18 Jun 2018, 11:00 pm Christopher Hein, notifications@github.com
wrote:

So as a method of packaging do you think for sig projects (and incubator
separate topic) we could potentially get a repo for a tap? It seems like
that would be a useful way for anyone to that makes sig owned projects;
would still require a PR but at least we’d be a little more in control of
it... might be a much bigger ask then I’m thinking


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/heptio/authenticator/issues/97#issuecomment-398283641,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPWS5jeV3ywnmKq80wpIHhbZYo9o0HXks5t-JOLgaJpZM4UiuYZ
.

Any updates on this since we've moved to SIG-owned repo?

Not that I know of, @errordeveloper, I wouldn't mind having either a sig-aws specific or kubernetes-sigs tap repository, whatever makes the most sense for the community. Thoughts?

I think tap per Github org would make most sense (i.e. https://github.com/kubernetes-sigs/homebrew-tap). I cannot think of a good reason of proposing SIG-specific taps, they would be in the same Github org anyway...

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

/remove-lifecycle stale

I think this is done @christopherhein

$ brew install aws-iam-authenticator
==> Downloading https://homebrew.bintray.com/bottles/aws-iam-authenticator-0.4.0.high_sierra.bottle.tar.gz
==> Downloading from https://akamai.bintray.com/7c/7c773fefb0506db8b95ed918ff639ede96b58a4d0d2a51d2faf941f30a61ad84?__gda__=exp=1556526410~hmac=5ee28ee1e8d417d6235dc0f2699e5ce2cb63e4e74adfc007f
######################################################################## 100.0%
==> Pouring aws-iam-authenticator-0.4.0.high_sierra.bottle.tar.gz
Error: The `brew link` step did not complete successfully
The formula built, but is not symlinked into /usr/local
Could not symlink bin/aws-iam-authenticator
Target /usr/local/bin/aws-iam-authenticator
already exists. You may want to remove it:
  rm '/usr/local/bin/aws-iam-authenticator'

To force the link and overwrite all conflicting files:
  brew link --overwrite aws-iam-authenticator

To list all files that would be deleted:
  brew link --overwrite --dry-run aws-iam-authenticator

Possible conflicting files are:
/usr/local/bin/aws-iam-authenticator
==> Summary
🍺  /usr/local/Cellar/aws-iam-authenticator/0.4.0: 5 files, 31.1MB
$

Thanks!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

nckturner picture nckturner  ·  6Comments

wbauern picture wbauern  ·  4Comments

thatrevguy picture thatrevguy  ·  11Comments

davidham picture davidham  ·  12Comments

tklebanoff picture tklebanoff  ·  6Comments