Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moving synced scratch org information between dev environments. #2385

Closed
Cerelius opened this issue Aug 1, 2023 · 2 comments
Closed

Moving synced scratch org information between dev environments. #2385

Cerelius opened this issue Aug 1, 2023 · 2 comments
Labels
feature Issue or pull request for a new feature

Comments

@Cerelius
Copy link

Cerelius commented Aug 1, 2023

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.

@Cerelius Cerelius added the feature Issue or pull request for a new feature label Aug 1, 2023
@github-actions
Copy link

github-actions bot commented Aug 1, 2023

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
Copy link

git2gus bot commented Aug 1, 2023

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

@forcedotcom forcedotcom locked and limited conversation to collaborators Aug 2, 2023
@WillieRuemmele WillieRuemmele converted this issue into discussion #2391 Aug 2, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
feature Issue or pull request for a new feature
Projects
None yet
Development

No branches or pull requests

1 participant