Streamline recreation of expired/stale CLI-managed connections
After refreshing a sandbox the connections in IC/SFDX are invalid. I typically create a “new” connection with the same name to reauthorize the org. A refresh button or similar to streamline that process (such as skipping the name prompt) would be a nice touch.
Comments (6)
-
reporter -
repo owner Excerpt from the original discussion on GDS Slack:
Requestors
i run into this when a sandbox is refreshed (so the refresh token isn’t helpful anymore)i usually get into this situation when it’s a sandbox connection and the sandbox gets refreshed. nukes all tokens and stuff
Me
Sounds like that's the main use case then. Yeah, re-auth with the same alias is the simplest way to address it, and I could certainly add a way to skip the prompts for the selected invalid OAuth connection if that's an interesting enhancement.Requestors
it’s interesting to me, since it saves a step I have to do fairly often and manually typing the same name is obviously subject to mistakes. I wouldn’t make it a huge priority though IMOsame
Me
My guess is that it's pretty simple to add, and I've already been mulling something similar for recreating an expired scratch org using the exact same info. That's also a pretty efficient operation now, but it is something like 4-5 clicks when it could perhaps be 1. Adding a "refresh this invalid CLI-based org using the same info" action for both use cases makes decent sense.
-
repo owner - removed version
- changed component to Connection Management
- marked as enhancement
-
repo owner - changed title to Streamline refreshing CLI-managed connections
-
repo owner - changed status to open
-
repo owner - changed title to Streamline recreation of expired/stale CLI-managed connections
- Log in to comment
https://gooddaysir.slack.com/archives/C0ZNTTU20/p1724176876702289