Dealing with credentials about sixtyfour HOT 5 CLOSED

I totally agree.

from sixtyfour.

Some ideas that come to mind:

• Should we use something like https://github.com/r-lib/oskeyring?
• Should we make a mini aws https://github.com/r-lib/gitcreds situation?
• Should we just force the user to set some env vars?

from sixtyfour.

Thanks! This feels like a situation where we should go with the dead simplest solution first, and add complexity if needed. That is:

• simple solution: make users set env vars in addition to whatever other aws creds method they have (if already using env vars then all set)
• more complex: add a package dependency e.g., oskeyring or gitcreds

from sixtyfour.

Lets stick with whatever paws does for now and think about solutions when/if we hit problems

from sixtyfour.

Allow users to set their AWS account within exported functions?

Possibly via some helper fxn, ideally not through every function, which would add extra work for everyone.

e.g., costexplorer has

costexplorer(
  config = list(),
  credentials = list(),
  endpoint = NULL,
  region = NULL
)

We initialize that list of functions for cost explorer ourselves - we could have helper funs to allow users to set creds so whenever it initializes they are used

from sixtyfour.