-
Notifications
You must be signed in to change notification settings - Fork 177
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
okta-aws passing profile name twice to aws CLI #375
Comments
Pretty sure this is related to #376, I think the fix is straightforward (see my comment). |
@hcourse-nydig yes, it appears to be the same issue (although the fix is slightly different for bash). |
hcourse-nydig
added a commit
to hcourse-nydig/okta-aws-cli-assume-role
that referenced
this issue
Aug 4, 2021
Removes first param from arg lists before calling aws cli. Fixes both bash and fish Resolves: oktadev#375, oktadev#376
If you've got time, could you double check the PR? This seems like a weirdly fundamental issue to still exist so I wonder if we're missing something? Anyway, should do the job! |
This was referenced Aug 4, 2021
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
On MacOS (and probably other linux), it seems that withokta isn't stripping the profile name from the arg list when it calls withokta using the following alias
All we get is a generic error from aws CLI complaining about bad arguments.
If the function is changed to
it seems to work fine, although I'm not sure that's the correct solution.
To Reproduce
Steps to reproduce the behavior:
okta-aws test sts get-caller-identity
Expected behavior
Get logged into the profile and get your caller identity.
The text was updated successfully, but these errors were encountered: