-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Respect user conventions #5802
Comments
Hi @monodhs, Thanks for your comment. Can you clarify, maybe with a concrete example, of what would change with this convention? What is it about the current implementation of configuration that is not working? It's also important to note that the AWS CLI is not specifically for Linux/BSD users, but also for Mac OSX and Windows. Also, configuration options can be set in a number of ways - through environment variables, configuration files, and fetched remotely via IMDS. |
Hi @monodhs, I found that this is a duplicate: #2433 This would be a very large change for existing AWS CLI users, and would be a convention that would need to be followed by all AWS SDKs and Tools. Could you please register your concerns on #2433 - I'm going to move that issue to the central AWS SDK issue tracking repository (https://github.com/aws/aws-sdk). Thanks again! |
|
Note: I did find the new issue (still open) at aws/aws-sdk#30 |
Confirm by changing [ ] to [x] below to ensure that it's a bug:
Describe the bug
For decades, there have been conventions on all serious platforms in place that allow
the battle-hardened and educated user to manage application data the way they see fit
and know best, supporting their individual data management policies and practices.
Some of those conventions are rudimentary or archaic even, and some indeed
empower the user; this issue is solely about the latter.
In the Linux and the open source BSD worlds, which are distinct from what's by the
general public referred to as "Unix" and, if by sheer luck, POSIX even, there exists a
standard called the XDG Base Directory Specification which, contrary to what the origin
of the specification might suggest, all self-respecting command line tools in these worlds
adhere to. The very Git SCM happens to be a prime example of such a tool.
This issue is to raise awareness about the specification and is asking for inclusion of all
users that make use of that specification into the communiy of awscli users.
SDK version number
This issue applies to all versions.
Platform/OS/Hardware/Device
Any Linux and open source BSD OS of the last decade; this is purely a software matter.
To Reproduce (observed behavior)
/usr/lib/python3/dist-packages/botocore> grep -RE "\.aws(/|')" *.py
Expected behavior
Evaluating and semantically adhering to the environment variables as defined
in the above referenced specification in order to obtain user-specific configuration
data and store user-specific application state -- including cached contents such
as SSO objects.
Logs/output
n/a
Additional context
The text was updated successfully, but these errors were encountered: