e5c6dca9c5
* Add new articles * Rename article * Add secrets content * Remove permissions statements * Fix image name * Fix article name * Mention GPG verification for Codespaces in "About commit signature verification" * Add GPG verification content * Add access and security procedure * Add 💅 * Rename articles * Rename the other article * Rename again * Okay, rename this one again, too * Update link * Start access and security content * Add 💅 * Mention new functionalities in "Personalizing..." * Mention new features in "About Codespaces" * Add 💅 * Fix typos * Add audit log events * Fix so many links * Add 💅 * Add permissions * Spell access correctly, for once * Add 💅 * FIX THESE LINKS I SWEAR * Addd missing ) * Start adding procedure * update with procedural * Update content/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces.md Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> * Update content/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.md Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> * Apply suggestions from code review Committing all reviews ✨ Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: Meg Bird <megbird@github.com>
2.8 KiB
title, intro, product, versions
| title | intro | product | versions | ||
|---|---|---|---|---|---|
| Managing encrypted secrets for Codespaces | You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables. | {% data reusables.gated-features.codespaces %} |
|
{% note %}
Note: Encrypted secrets for {% data variables.product.prodname_codespaces %} is currently in beta and subject to change.
{% endnote %}
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
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.
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.
