dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Apply suggestions from code review 

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:19 +00:00 committed by GitHub
parent ad8835cfa3
commit 1a24364b34
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
daprdocs/content/en/concepts/components-concept.md
View File

@ -54,11 +54,11 @@ For more information read [Pluggable components overview]({{< ref "pluggable-com
## Hot Reloading
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.
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.
There will be 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