Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-5942

Extension secrets are lost on workspace restart

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Release Notes
    • Hide
      = Extension secrets are lost on workspace restart

      Extension secrets for Visual Studio Code - Open Source ("Code - OSS") are no longer lost after workspace restart, but encrypted and persisted in the browser's local storage. This allows extensions like link:https://open-vsx.org/extension/redhat/ansible[Ansible] that use Visual Studio Code link:https://code.visualstudio.com/api/references/vscode-api#SecretStorage[Secrets Storage API] to persist the data between workspace restarts in the same browser.
      Show
      = Extension secrets are lost on workspace restart Extension secrets for Visual Studio Code - Open Source ("Code - OSS") are no longer lost after workspace restart, but encrypted and persisted in the browser's local storage. This allows extensions like link: https://open-vsx.org/extension/redhat/ansible [Ansible] that use Visual Studio Code link: https://code.visualstudio.com/api/references/vscode-api#SecretStorage [Secrets Storage API] to persist the data between workspace restarts in the same browser.
    • Bug Fix
    • Done

      Description of problem:

      Some extensions are using Secrets Plugin API https://code.visualstudio.com/api/advanced-topics/remote-extensions#persisting-secrets

      Seems at the moment secrets are not persisted to the file system / secret storage and appeared to be lost when workspace restart.

      Upstream Issue: https://github.com/eclipse/che/issues/22837

      https://github.com/Nykredit/openshift-test/issues/10

       

      For example: 

      SonarLint extension [1] in Dev Spaces 3.11. The extension allows to generate and install a token for communicating with a Sonar server endpoint. The generation works fine - but if the Dev Spaces workspace in question is restarted, then the token is lost upon relaunch.

      The extension uses the generic VSCode SecretStorage API to store the data of the token

       

      [1] Extension ID: SonarSource.sonarlint-vscode
      [2] https://github.com/SonarSource/sonarlint-vscode/blob/4.2.2%2B75910/src/settings/connectionsettings.ts#L66

      Prerequisites (if any, like setup, operators/versions):{}

      Steps to Reproduce

       https://github.com/eclipse/che/issues/22837

       

      Actual results:

      Secrets are not getting persisted

      Expected results:

      Secrets must be persisted

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Acceptance criteria: 

       

      Definition of Done:

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

       

       *

              vgulyy Vitaliy Gulyy (Inactive)
              rhn-support-gio Ginilekshmi A O (Inactive)
              Maksym Musienko Maksym Musienko
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: