Fix iam create-virtual-mfa-device to work with relative output paths. #1002
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
http://docs.aws.amazon.com/cli/latest/reference/iam/create-virtual-mfa-device.html
If you specify output filename with relative path for iam-CreateVirtualMFADevice, you end up with write error
If you specify absolute path(like
/tmp/QRCode.png
), this works just fine.This is because
aws
checks foroutfile
' s write availability before it actually writes to it, and this is done throughoutfile
's parent directory's write permission. So if you cannot restoreoutfile
's parent path from given argument,os.access(parent_dir, os.W_OK)
always fails.