Update daprdocs/content/en/concepts/components-concept.md

Co-authored-by: Mark Fussell <markfussell@gmail.com>
Signed-off-by: Josh van Leeuwen <me@joshvanl.dev>
This commit is contained in:
Josh van Leeuwen 2024-01-09 13:37:50 +00:00 committed by GitHub
parent 1a24364b34
commit 7271911f32
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions

View File

@ -57,7 +57,7 @@ For more information read [Pluggable components overview]({{< ref "pluggable-com
With the [`HotReload` feature enabled]({{< ref "support-preview-features.md" >}}), components are able to be "hot reloaded" at runtime. With the [`HotReload` feature enabled]({{< ref "support-preview-features.md" >}}), components are able to be "hot reloaded" at runtime.
This means that you can update component configuration without restarting the Dapr runtime. This means that you can update component configuration without restarting the Dapr runtime.
Component reloading happens when a component resource is created, updated, or deleted, either in the Kubernetes API or in Self Hosted mode when a file is changed in the `resources` directory. Component reloading happens when a component resource is created, updated, or deleted, either in the Kubernetes API or in Self Hosted mode when a file is changed in the `resources` directory.
When a component is updated, the Component is first closed, and then reinitialized using the new configuration. When a component is updated, the component is first closed, and then reinitialized using the new configuration.
There is a short period of time where the component is unavailable during the duration of the reload until the component is reinitialized. There is a short period of time where the component is unavailable during the duration of the reload until the component is reinitialized.
## Available component types ## Available component types