Skip to content

Commit

Permalink
Update modules/administration-guide/pages/trusted-extensions-for-micr…
Browse files Browse the repository at this point in the history
…osoft-visual-studio-code.adoc

Co-authored-by: Jana Vrbkova <jvrbkova@redhat.com>
  • Loading branch information
vitaliy-guliy and deerskindoll authored Apr 9, 2024
1 parent 2de0560 commit 5a68f97
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Use the `trustedExtensionAuthAccess` field with caution as it could potentially
.Procedure
[IMPORTANT]
====
Since the Visual Studio Code editor is bundled within `che-code` image, you can only change the `product.json` file when the workspace is started up.
Since the Microsoft Visual Studio Code editor is bundled within `che-code` image, you can only change the `product.json` file when the workspace is started up.
====

The first you need to define __VSCODE_TRUSTED_EXTENSIONS__ environment variable and specify one or several extensions separated by comma. The value of the variable will be taken and parsed right after workspace is started and the corresponding `trustedExtensionAuthAccess` section will be added to the `product.json` right before the Visual Studio Code is started.
Expand Down

0 comments on commit 5a68f97

Please sign in to comment.