From 4b35f6547736ddcb0a6bb0694a2fdcce4318799b Mon Sep 17 00:00:00 2001 From: a-r-j-a-n Date: Sun, 20 Oct 2019 09:21:53 +0200 Subject: [PATCH] Update secrets.markdown (#10864) Change because http password moved to auth providers. --- source/_docs/configuration/secrets.markdown | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/source/_docs/configuration/secrets.markdown b/source/_docs/configuration/secrets.markdown index 4264c7dbe6c..c9d108f9282 100644 --- a/source/_docs/configuration/secrets.markdown +++ b/source/_docs/configuration/secrets.markdown @@ -13,15 +13,19 @@ The workflow for moving private information to `secrets.yaml` is very similar to The entries for password and API keys in the `configuration.yaml` file usually looks like the example below. ```yaml -http: - api_password: YOUR_PASSWORD +homeassistant: + auth_providers: + - type: legacy_api_password + api_password: YOUR_PASSWORD ``` Those entries need to be replaced with `!secret` and an identifier. ```yaml -http: - api_password: !secret http_password +homeassistant: + auth_providers: + - type: legacy_api_password + api_password: !secret http_password ``` The `secrets.yaml` file contains the corresponding password assigned to the identifier.