Skip to content

Remove docs for removed keyring/credstash options #16745

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
frenck merged 6 commits into from
Feb 25, 2021
Merged

Remove docs for removed keyring/credstash options #16745

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
4b59a56
Delete credstash.markdown
hmmbob Feb 25, 2021
b4407a9
Delete keyring.markdown
hmmbob Feb 25, 2021
becf87c
Remove credstash and keyring links
hmmbob Feb 25, 2021
718407f
Removing keyring, credstash from sidebar
hmmbob Feb 25, 2021
df80f07
Add keyring, credstash redirect
hmmbob Feb 25, 2021
47a2a7d
Remove leftover keyring reference
hmmbob Feb 25, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 1 addition & 7 deletions source/_docs/configuration/secrets.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,8 +38,7 @@ http_password: YOUR_PASSWORD
When you start splitting your configuration into multiple files, you might end up with configuration in sub folders. Secrets will be resolved in this order:

- A `secrets.yaml` located in the same folder as the 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 `configuration.yaml`,
- lastly, `keyring` will be queried for the secret (more info below).
- next, parent folders will be searched for a `secrets.yaml` file with the secret, stopping at the folder with the main `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.

Expand All @@ -58,8 +57,3 @@ hass --script check_config --secrets
```

This will print all your secrets.

## Alternatives to `secrets.yaml`

- [Using a keyring that is managed by your OS to store secrets](/docs/tools/keyring/)
- [Storing passwords securely in AWS](/docs/tools/credstash/)
35 changes: 0 additions & 35 deletions source/_docs/tools/credstash.markdown
View file
Open in desktop

This file was deleted.

39 changes: 0 additions & 39 deletions source/_docs/tools/keyring.markdown
View file
Open in desktop

This file was deleted.

2 changes: 0 additions & 2 deletions source/_includes/asides/docs_navigation.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,8 +146,6 @@ <h1 class="title delta">Topics</h1>
<li>{% active_link /docs/tools/quick-bar/ Quick Bar %}</li>
<li>{% active_link /docs/tools/hass/ hass %}</li>
<li>{% active_link /docs/tools/check_config/ check_config %}</li>
<li>{% active_link /docs/tools/credstash/ credstash %}</li>
<li>{% active_link /docs/tools/keyring/ keyring %}</li>
</ul>
</li>
<li>
Expand Down
2 changes: 2 additions & 0 deletions source/_redirects
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2190,6 +2190,8 @@
/docs/installation/raspberry-pi-all-in-one /getting-started
/getting-started/hassbian /getting-started
/getting-started/installation-raspberry-pi-all-in-one /getting-started
/docs/tools/keyring/ /docs/configuration/secrets
/docs/tools/credstash/ /docs/configuration/secrets

# Blog
/blog/2019/05/29/release-94 /blog/2019/06/05/release-94
Expand Down