-
Notifications
You must be signed in to change notification settings - Fork 34
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
v2.1.0 Hasn't been published via Chocolatey #186
Comments
Thanks @officeSpacePirate I'm looking into this. |
Thanks for your request. You're right, releases via Chocolatey are new, and we're planning to automate releases soon. Thanks for your patience! Internal Ref: OKTA-700629 |
Thanks for the quick response. Obviously not an emergency, but looking forward to the new changes. |
Will the amd64 builds resume soon? |
@lw-cchapin did you see the note in the v2.0.1 release ? We are no longer producing an amd64 build because binaries built from golang for amd64 are notable across the board for triggering various AVs. Can you get by with an i386 build? I don't have a Windows background, and thought any amd64 machine can run i386 binaries. please adjust my understanding. I want to get this right for you, but also having amd64 false positives is not a good confidence booster in general. |
Any updates on this one? Thanks! |
I'm in the process of writing a GH action for this publish a Chocolatey release when we do a GH release. |
ok v2.2.0 has been submitted via github action https://community.chocolatey.org/packages/okta-aws-cli#versionhistory |
Looks like the latest release via Chocolatey is v2.0.1. It also looks like Chocolatey support is new, so perhaps that part hasn't been automated?
Anyway, the business I work for is looking to switch to this tool from saml2aws soon, so the Windows support is much appreciated in advance. Updated documentation would be helpful if you guys haven't already started on that.
The text was updated successfully, but these errors were encountered: