Shared Connect configuration across client packages

I seem to be using connectapi more and more frequently:

• Building adhoc admin scripts using connectapi directly
• Building our CI/CD scripts using connectapi directly
• Writing scripts, apps, and report which use pins - using https://github.com/rstudio/pins-r/blob/main/R/board_connect.R
• Writing plumber client apps using our own client package (built on top of https://github.com/slodge/rapiclient - currently working out if we can publish this somehow... depends on plumber changes anyway - so won't happen soon)

All of these usages seem to somehow end up using their own custom conventions for connect connections - e.g. pins with its c("auto", "manual", "envvar", "rsconnect") setup.

Is it worth implementing a standard set of ways to configure Connect connections so that users can set these up once and then use any connectapi-dependent package? If so, should connectapi be the place for this?

No repository file or test is named in the issue. Start by reviewing the existing connection conventions in connectapi and pins-r's R/board_connect.R, then compare how the mentioned client packages configure Connect connections. Done means agreeing on whether a shared configuration belongs in connectapi and defining an implementable standard.