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
aws-okta: init at 0.19.0 #44819
aws-okta: init at 0.19.0 #44819
Conversation
@GrahamcOfBorg build aws-okta |
Success on aarch64-linux (full log) Attempted: aws-okta Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: aws-okta Partial log (click to expand)
|
Success on x86_64-darwin (full log) Attempted: aws-okta Partial log (click to expand)
|
One issue with this PR - the size of the |
@imalsogreg I don't think we should fork it. We can always nuke the vendor directory during the build. Trying to find someone with the know-how on when and when not to unvendor. :) |
#nixos (two data points, so obviously representative) says vendoring is fine, so if you'll just get rid of the comments, we can go ahead and merge. :) |
dc81a6f
to
24fa3c2
Compare
@GrahamcOfBorg build aws-okta |
I force-pushed a commit to my PR branch that removes the unneeded comment and extra |
@GrahamcOfBorg build aws-okta |
Success on aarch64-linux (full log) Attempted: aws-okta Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: aws-okta Partial log (click to expand)
|
Success on x86_64-darwin (full log) Attempted: aws-okta Partial log (click to expand)
|
Motivation for this change
Adding a useful tool for people that need to use Okta for AWS cli access. This package could also be used later in an okta-aws nixos module if we want to provide a less imperative okta login.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)