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
{{ message }}
This repository has been archived by the owner on Mar 5, 2021. It is now read-only.
As for now the only way to save credentials I know is to export AWS env variables and run credulous save
The problem here is that export commands stay in bash history and can be easily recovered.
Expected: when there is no AWS credentials available in environment, credulous save will expect them in the standard input, in the form provided by AWS. For example:
$ credulous save
No AWS credentials found in env, please enter them now:
Access Key ID: AKIAJ43JGF5FHJMXPKTQ
Secret Access Key: gQ00RQOHIwXK+Xb+cBfvSYSDLw+ioc3KeIOPYGw
Enter passphrase: *******
Successfully saved to user@account
The text was updated successfully, but these errors were encountered:
As for now the only way to save credentials I know is to export AWS env variables and run
credulous save
The problem here is that export commands stay in bash history and can be easily recovered.
Expected: when there is no AWS credentials available in environment,
credulous save
will expect them in the standard input, in the form provided by AWS. For example:The text was updated successfully, but these errors were encountered: