diff --git a/daprdocs/content/en/operations/configuration/secret-scope.md b/daprdocs/content/en/operations/configuration/secret-scope.md index a26575ca14d..d32cad36f2f 100644 --- a/daprdocs/content/en/operations/configuration/secret-scope.md +++ b/daprdocs/content/en/operations/configuration/secret-scope.md @@ -4,7 +4,6 @@ title: "How-To: Limit the secrets that can be read from secret stores" linkTitle: "Limit secret store access" weight: 3000 description: "Define secret scopes by augmenting the existing configuration resource with restrictive permissions." -description: "Define secret scopes by augmenting the existing configuration resource with restrictive permissions." --- In addition to [scoping which applications can access a given component]({{% ref "component-scopes.md"%}}), you can also scope a named secret store component to one or more secrets for an application. By defining `allowedSecrets` and/or `deniedSecrets` lists, you restrict applications to access only specific secrets. diff --git a/daprdocs/layouts/_partials/hooks/head-end.html b/daprdocs/layouts/_partials/hooks/head-end.html index a86318b4883..26e604a4cfc 100644 --- a/daprdocs/layouts/_partials/hooks/head-end.html +++ b/daprdocs/layouts/_partials/hooks/head-end.html @@ -1,25 +1,3 @@ {{ with .Site.Params.search.algolia }} - - {{ end }} \ No newline at end of file