7b142730bf
* Mention dependency files update for Gradle * Adding more specific caveats of apply support. Co-authored-by: Mike McDonald <2575327+asciimike@users.noreply.github.com> * Adding ip_allow_list entries I've added the ip_allow_list and ip_allow_list_entry category actions * Update backing-up-a-repository.md Add Azure Blob Storage as potential backup or storage service to have more options and especially also call out a non-consumer service with SLAs. * Add missing "Open Git Bash" step * Update data/reusables/dependabot/supported-package-managers.md * Update about-linked-identities.md * Update viewing-and-managing-a-members-saml-access-to-your-organization.md * Update viewing-and-managing-a-users-saml-access-to-your-enterprise.md * Fix workflow command for toolkit function (#10249) * fixed typographical errors * Update CONTRIBUTING.md * Fixed typographical errors * Apply suggestions from code review * Add 💅 * Move mention of SCIM * Add newline * Add Further Reading Links Fixes github#9906 * Fix link * Add Further Reading Links Fixes github#9906 * 🔀 linking Fixes github#9906 * 🔀 linking * 🔀 linking * Added further reading section * Update content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> * Update content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> * Update content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md * Apply suggestions from code review * Update device flow OAuth app responses (#10426) Co-authored-by: Zbynek Konecny <zbynek1729@gmail.com> Co-authored-by: Mike McDonald <2575327+asciimike@users.noreply.github.com> Co-authored-by: Jonathan Cardona <Hollywood@github.com> Co-authored-by: Gerwald Oberleitner <gerwaldo@users.noreply.github.com> Co-authored-by: Rob Cowsill <42620235+rcowsill@users.noreply.github.com> Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Co-authored-by: Andre Kolodochka <59625655+andrekolodochka@users.noreply.github.com> Co-authored-by: Lee Dohm <1038121+lee-dohm@users.noreply.github.com> Co-authored-by: Abshar Mohammed Aslam <Absharaslam2001@gmail.com> Co-authored-by: Lulu <oluchi@lulunwenyi.com> Co-authored-by: Oluchi Nwenyi <dev@lulunwenyi.com> Co-authored-by: Ramya Parimi <ramyaparimi@github.com> Co-authored-by: James M. Greene <JamesMGreene@github.com> Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> Co-authored-by: Laura Coursen <lecoursen@github.com> Co-authored-by: PSJ <51746608+thispsj@users.noreply.github.com> Co-authored-by: Janice <janiceilene@github.com> Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>
3.8 KiB
title, intro, product, versions, redirect_from, type, topics, shortTitle
| title | intro | product | versions | redirect_from | type | topics | shortTitle | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Managing encrypted secrets for your codespaces | You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables. | {% data reusables.gated-features.codespaces %} |
|
|
how_to |
|
Encrypted secrets |
About encrypted secrets for {% data variables.product.prodname_codespaces %}
You can add encrypted secrets to your user account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets.
- Personal access tokens to cloud services
- Service principals
- Subscription identifiers
- Credentials for a private image registry
You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret.
{% data reusables.codespaces.secrets-on-start %}
Naming secrets
{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository.
{% data reusables.codespaces.secret-precedence %}
Limits for secrets
You can store up to 100 secrets for {% data variables.product.prodname_codespaces %}.
Secrets are limited to 64 KB in size.
Adding a secret
{% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %}
- To the right of "Codespaces secrets", click New secret.
- Under "Name", type a name for your secret.
{% data reusables.user_settings.codespaces-secret-value %}
{% data reusables.user_settings.codespaces-secret-repository-access %} - Click Add secret.
Editing a secret
You can update the value of an existing secret, and you can change which repositories can access a secret.
{% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %}
- Under "Codespaces secrets", to the right of the secret you want to edit, click Update.
- Under "Value", click enter a new value.
{% data reusables.user_settings.codespaces-secret-value %}
{% data reusables.user_settings.codespaces-secret-repository-access %} - Optionally, to remove the secret's access to a repository, deselect the repository.
- Click Save changes.
Deleting a secret
{% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %}
- Under "Codespaces secrets", to the right of the secret you want to delete, click Delete.
- Read the warning, then click OK.
