jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-22 11:26:57 -05:00
Code Issues Projects Releases Wiki Activity

Codespaces: change 'encrypted secrets' to 'secrets' (#41416)

Browse Source
This commit is contained in:
hubwriter
2023-09-04 11:25:21 +01:00
committed by GitHub
parent bec13b6e58
commit 57d47a08af
57 changed files with 111 additions and 105 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
content/codespaces/developing-in-codespaces/persisting-environment-variables-and-temporary-files.md
View File

@@ -30,7 +30,7 @@ There are three ways that you can set persistent custom environment variables fo
- You can edit the `devcontainer.json` configuration file for the repository
- You can use a custom Dockerfile
- You can use encrypted secrets
- You can use secrets
#### Edit the `devcontainer.json` configuration file for the repository
@@ -44,7 +44,7 @@ Edit the `devcontainer.json` configuration file for the repository, and use the
}
```
Only use this method for values that you are happy to commit to your repository as plaintext. For sensitive values such as access tokens, use encrypted secrets.
Only use this method for values that you are happy to commit to your repository as plaintext. For sensitive values such as access tokens, use secrets.
The environment variable will be set within your editor's remote server process, and will be available for sub-processes of that remote server process, such as terminals and debugging sessions. However, the variable will not be available more broadly inside the container. This method is useful if you don't need the environment variable to be set for other background processes that run at startup, and if you are using a premade image and don't have or want a custom Dockerfile.
@@ -58,9 +58,9 @@ This method is useful if you already have a Dockerfile and want to set a variabl
This setting will take effect when you rebuild your container or create a new codespace after pushing this change to the repository. For more information about applying configuration changes to a codespace, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)."
#### Use encrypted secrets
#### Use secrets
You can use encrypted secrets for {% data variables.product.prodname_github_codespaces %} to set custom variables for codespaces created for the repository. For more information, see "[AUTOTITLE](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."
You can use secrets for {% data variables.product.prodname_github_codespaces %} to set custom variables for codespaces created for the repository. For more information, see "[AUTOTITLE](/codespaces/managing-your-codespaces/managing-secrets-for-your-codespaces)."
You should use this method for environment variable values that you do not want to commit to the repository as plaintext.