You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This works perfectly with the AWS CLI. However, it doesn't work with ExAWS (using configparser_ex), since it only splits the value of credential_process on whitespace without understanding quoted values. The resulting function call looks like:
...which throws an ENOENT since there is no such file as "/home/me/.aws/op-cred-helper.sh" (quotes included!). As a workaround I can remove all the quotes, but then there cannot be spaces anywhere in the file path, vault name, or item name, otherwise the command isn't constructed correctly. (Fortunately 1Password allows referring to vaults/items using unique IDs that don't contain spaces, so this is only a real problem if the file path contains a space.)
I use 1Password to store my AWS credentials, and initially set up my
~/.aws/config
like this:This works perfectly with the AWS CLI. However, it doesn't work with ExAWS (using
configparser_ex
), since it only splits the value ofcredential_process
on whitespace without understanding quoted values. The resulting function call looks like:...which throws an
ENOENT
since there is no such file as"/home/me/.aws/op-cred-helper.sh"
(quotes included!). As a workaround I can remove all the quotes, but then there cannot be spaces anywhere in the file path, vault name, or item name, otherwise the command isn't constructed correctly. (Fortunately 1Password allows referring to vaults/items using unique IDs that don't contain spaces, so this is only a real problem if the file path contains a space.)credentials_process
is documented to support quoted paths/arguments here: https://docs.aws.amazon.com/sdkref/latest/guide/feature-process-credentials.htmlThe text was updated successfully, but these errors were encountered: