Moving synced scratch org information between dev environments.

[Cerelius]

I'm frustrated when trying to work on a single scratch org across multiple environments. I can't move the .sf and .sfdx directories that are generated in the local environment to a different location because they use absolute paths and are encrypted. I'd like to be able to relocate the configuration without losing my source tracking information for the scratch org that I am authenticated to.

In the past I could do this by moving the .sfdx directory and updating the path to match the new destination. Because the files are encrypted that won't work anymore.

Ideally they could use a relative pathing instead of an absolute path so the movement to a new directory does not break the configuration. I don't know why the encryption is in place but removing the encryption would be fine from my perspective. Although, I understand there may be reasons for it that I'm not aware of.

[github-actions[bot]]

Thank you for filing this feature request. We appreciate your feedback and will review the feature at our next grooming or sprint planning session. We prioritize feature requests with more upvotes and comments.

[git2gus[bot]]

This issue has been linked to a new work item: W-13866632

[mshanemc]

Storing unencrypted Access/Refresh tokens isn't safe enough for Salesforce.

You didn't mention what OS you're on--for example, macos will use its native keychain by default.

There is an environment variable SF_USE_GENERIC_UNIX_KEYCHAIN https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_env_variables.htm that lets you opts out of that behavior so that the CLI creates a key.json in the CLI's folder. That then should be more portable.

We have a different Discussion around making the CLI's home dir more configurable #2373 which might also help with your portability use case