-
Notifications
You must be signed in to change notification settings - Fork 36
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
fix: extension secrets should not be lost when workspace restart #340
Conversation
Signed-off-by: vitaliy-guliy <[email protected]>
Pull Request Dev image published: |
Pull Request Che-Code image published: |
Signed-off-by: vitaliy-guliy <[email protected]>
Pull Request Dev image published: |
Pull Request Che-Code image published: |
Signed-off-by: vitaliy-guliy <[email protected]>
Pull Request Dev image published: |
Signed-off-by: vitaliy-guliy <[email protected]>
Pull Request Dev image published: |
Pull Request Che-Code image published: |
Pull Request Dev image published: |
Pull Request Che-Code image published: |
Pull Request Dev image published: |
Pull Request Che-Code image published: |
Signed-off-by: vitaliy-guliy <[email protected]>
Pull Request Dev image published: |
Pull Request Che-Code image published: |
Signed-off-by: vitaliy-guliy <[email protected]>
Pull Request Dev image published: |
Pull Request Che-Code image published: |
Pull Request Dev image published: |
Pull Request Che-Code image published: |
Signed-off-by: vitaliy-guliy <[email protected]>
Pull Request Dev image published: |
Signed-off-by: vitaliy-guliy <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vitaliy-guliy thanks for providing the test projects and steps for testing the PR.
I tested the PR following the suggested instructions. In a new workspace, I was able to get the secret, stored in another workspace.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works good with the Ansible extension
screencast-bpconcjcammlapcogcnnelfmaeghhagj-2024.05.15-19_27_00.mp4
Co-authored-by: Valerii Svydenko <[email protected]>
Co-authored-by: Valerii Svydenko <[email protected]>
Co-authored-by: Valerii Svydenko <[email protected]>
Co-authored-by: Valerii Svydenko <[email protected]>
Co-authored-by: Valerii Svydenko <[email protected]>
Co-authored-by: Valerii Svydenko <[email protected]>
Co-authored-by: Valerii Svydenko <[email protected]>
Co-authored-by: Valerii Svydenko <[email protected]>
Co-authored-by: Valerii Svydenko <[email protected]>
Pull Request Dev image published: |
Co-authored-by: Valerii Svydenko <[email protected]>
Pull Request Dev image published: |
Co-authored-by: Valerii Svydenko <[email protected]>
Pull Request Dev image published: |
Co-authored-by: Valerii Svydenko <[email protected]>
Pull Request Dev image published: |
2 similar comments
Pull Request Dev image published: |
Pull Request Dev image published: |
Pull Request Che-Code image published: |
Verification completed from my side |
What does this PR do?
Allows to keep encrypted extension secrets in the browser local storage.
Launcher output
What issues does this PR fix?
eclipse-che/che#22837
How to test this PR?
Create a workspace with
https://github.com/vitaliy-guliy/vscode-test-extension/tree/persisting-secrets?che-editor=https://gist.githubusercontent.com/vitaliy-guliy/4fedeef3dbf8e902af94240780c442e6/raw/f08e91485b8529c6761b73f375fccde8d62ae94f/editor.yaml&new
Build test extension from sources or download the binary from https://github.com/vitaliy-guliy/vscode-test-extension/releases/tag/0.0.2
Go to extensions view, install the extension from .vsix file
Run
Secrets: Add secret
command and add the secret entering any valueDelete the workspace and create it again with the link above, or just restart the workspace (chose what do you prefer). If you recreated workspace, it needs to install test extension again.
Run
Secrets: Get Secret
command. You should get the value entered before.You can create any workspace using
che-code
image provided by this pull request and experiment with any extension you want. For instance, it is possible to install sonarlint extension, open extension settings, configure it and then restart the workspace. All the settings should be saved.Does this PR contain changes that override default upstream Code-OSS behavior?
git rebase
were added to the .rebase folder