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
Presently with #16, we support lazy-loading of credential files when a qualified profile URI is used. If you have a profile named dev in ~/.aws/credentials.d/92-something.gpg, the profile URI will be dev/92-something; if stg exists in ~/.aws/credentials, then the profile URI will be /stg.
Currently, lazy-loading works for root URIs, but if a non-root profile URI is used, we load all profiles rather than incrementally try to load by the file stem. The most optimal solution would be to lazy load like this:
✔️ If passed a root URI:
Load the root credentials file and return profile if found.
Load all credentials and return profile if found.
🚫 If passed a non-root URI:
Load files matching the profile URI prefix as a file stem, and return profile if found.
Load all credentials and return profile if found.
✔️ If passed a profile name and not a URI, load all files and return profile if found.
Implementing the non-root URI lazy-loading is what is required by this issue.
The text was updated successfully, but these errors were encountered:
Presently with #16, we support lazy-loading of credential files when a qualified profile URI is used. If you have a profile named
dev
in~/.aws/credentials.d/92-something.gpg
, the profile URI will bedev/92-something
; ifstg
exists in~/.aws/credentials
, then the profile URI will be/stg
.Currently, lazy-loading works for root URIs, but if a non-root profile URI is used, we load all profiles rather than incrementally try to load by the file stem. The most optimal solution would be to lazy load like this:
Implementing the non-root URI lazy-loading is what is required by this issue.
The text was updated successfully, but these errors were encountered: