jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-14 12:56:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Secrets remove core specific steps (#39188)

Browse Source
This commit is contained in:
c0ffeeca7 2025-05-26 12:35:55 +02:00 committed by GitHub
parent 4c1d353dab
commit fc14b5d413
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 5 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
source/_docs/blueprint/selectors.markdown
View File

@ -83,7 +83,7 @@ The output of this selector is a list of actions. For example:
## Add-on selector
This can only be used on Home Assistant Operating System installation. For Home Assistant Container installations, an error will be displayed.
This can only be used on a {% term "Home Assistant Operating System" %} installation. For {% term "Home Assistant Container" %} installations, an error will be displayed.
The add-on selector allows the user to input an add-on slug.
On the user interface, it will list all installed add-ons and use the slug of the
@ -275,7 +275,8 @@ assist_pipeline:
## Backup location selector
This can only be used on an installation with a Home Assistant Operating System. For {% term "Home Assistant Container" %} installations, an error
This can only be used on an installation with a {% term "Home Assistant Operating System" %}. For {% term "Home Assistant Container" %} installations, an error
will be displayed.
The backup location selector shows a list of places a backup could go, depending

12
source/_docs/configuration/secrets.markdown
View File

@ -51,20 +51,12 @@ When you start splitting your configuration into multiple files, you might end u
- A `secrets.yaml` located in the same folder as the {% term YAML %} file referencing the secret,
- next, parent folders will be searched for a `secrets.yaml` file with the secret, stopping at the folder with the main {% term "`configuration.yaml`" %}.
To see where secrets are being loaded from, you can either add an option to your `secrets.yaml` file or use the `check_config` script. The latter is only available for {% term "Home Assistant Core" %} installations given it's available through [`hass`](/docs/tools/hass/).
To see where secrets are being loaded from, you can add an option to your `secrets.yaml` file.
*Option 1*: Print where secrets are retrieved from to the Home Assistant log by adding the following to `secrets.yaml`:
Print where secrets are retrieved from to the Home Assistant log by adding the following to `secrets.yaml`:
```yaml
logger: debug
```
This will not print the actual secret's value to the log.
*Option 2*: For Home Assistant Core installations, you can also view where secrets are retrieved from and the contents of all `secrets.yaml` files using the [`check_config` script](/docs/tools/check_config/) from the command line:
```bash
hass --script check_config --secrets
```
This will print all your secrets.