Skip to content

docs: Graduate Component HotReloading to GA#5162

Open
javier-aliaga wants to merge 5 commits into
dapr:v1.18from
javier-aliaga:docs/hotreload-ga
Open

docs: Graduate Component HotReloading to GA#5162
javier-aliaga wants to merge 5 commits into
dapr:v1.18from
javier-aliaga:docs/hotreload-ga

Conversation

@javier-aliaga
Copy link
Copy Markdown
Contributor

Reflect dapr/dapr#9577 and dapr/dapr#9811: HotReload is on by default in v1.18. Remove the preview rows and update prose to default-on with an opt-out note.

Thank you for helping make the Dapr documentation better!

Please follow this checklist before submitting:

  • Commits are signed with Developer Certificate of Origin (DCO - learn more)
  • Read the contribution guide
  • Commands include options for Linux, MacOS, and Windows within tabpane
  • New file and folder names are globally unique
  • Page references use shortcodes instead of markdown or URL links
  • Images use HTML style and have alternative text
  • Places where multiple code/command options are given have tabpane

In addition, please fill out the following to help reviewers understand this pull request:

Description

Issue reference

@javier-aliaga javier-aliaga marked this pull request as ready for review May 13, 2026 09:25
@javier-aliaga javier-aliaga requested review from a team as code owners May 13, 2026 09:25
Reflect dapr/dapr#9577 and dapr/dapr#9811: HotReload is on by default
in v1.18. Remove the preview rows and update prose to default-on with
an opt-out note.

Signed-off-by: Javier Aliaga <javier@diagrid.io>
Copy link
Copy Markdown
Member

@msfussell msfussell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@javier-aliaga. Reviewed. Additional changes needed

Comment thread daprdocs/content/en/operations/components/component-updates.md Outdated
## Hot Reloading

When the [`HotReload` feature gate]({{% ref "support-preview-features" %}}) is enabled, changes to Configuration resources are automatically detected and trigger a graceful restart of the Dapr sidecar (via SIGHUP) to apply the new configuration. Unchanged Configuration resources are silently ignored. SIGHUP is not supported on Windows.
Since Dapr v1.18, changes to Configuration resources are automatically detected and trigger a graceful restart of the Dapr sidecar (via SIGHUP) to apply the new configuration. Unchanged Configuration resources are silently ignored. SIGHUP is not supported on Windows. To opt out, disable the `HotReload` feature in the [Dapr application configuration]({{% ref "preview-features.md" %}}).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Since Dapr v1.18, changes to Configuration resources are automatically detected and trigger a graceful restart of the Dapr sidecar (via SIGHUP) to apply the new configuration. Unchanged Configuration resources are silently ignored. SIGHUP is not supported on Windows. To opt out, disable the `HotReload` feature in the [Dapr application configuration]({{% ref "preview-features.md" %}}).
Changes to Configuration resources are automatically detected and trigger a graceful restart of the Dapr sidecar (via SIGHUP) to apply the new configuration. Unchanged Configuration resources are silently ignored. SIGHUP is not supported on Windows. To opt out, disable the `HotReload` feature in the [Dapr application configuration]({{% ref "preview-features.md" %}}).

## Hot Reloading

When the [`HotReload` feature gate]({{% ref "support-preview-features" %}}) is enabled, changes to Configuration resources are automatically detected and trigger a graceful restart of the Dapr sidecar (via SIGHUP) to apply the new configuration. Unchanged Configuration resources are silently ignored. SIGHUP is not supported on Windows.
Since Dapr v1.18, changes to Configuration resources are automatically detected and trigger a graceful restart of the Dapr sidecar (via SIGHUP) to apply the new configuration. Unchanged Configuration resources are silently ignored. SIGHUP is not supported on Windows. To opt out, disable the `HotReload` feature in the [Dapr application configuration]({{% ref "preview-features.md" %}}).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We cannot have a feature that does not work on Windows. This has to be fixed.
Also Are you saying the just Configuration resources uses SIGHUP, or that any hot reloading does not work on Windows.

Copy link
Copy Markdown
Member

@msfussell msfussell May 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this works on Windows and Linux, no need to talk about the implementation in the docs. Just say

"Changes to Configuration resources are automatically detected and trigger a graceful restart of the Dapr sidecar to apply the new configuration. To opt out, disable the HotReload feature in the [Dapr application configuration]({{% ref "configuration-overview.md" %}})"

You need to update the https://docs.dapr.io/operations/configuration/configuration-overview/ application configuration section to add the hot reload feature into the list and then reference it here.

## Hot Reloading

When the [`HotReload` feature gate]({{% ref "support-preview-features" %}}) is enabled, changes to Resiliency resources are automatically detected and trigger a graceful restart of the Dapr sidecar (via SIGHUP) to apply the updated resiliency policies. Unchanged Resiliency resources are silently ignored. SIGHUP is not supported on Windows.
Since Dapr v1.18, changes to Resiliency resources are automatically detected and trigger a graceful restart of the Dapr sidecar (via SIGHUP) to apply the updated resiliency policies. Unchanged Resiliency resources are silently ignored. SIGHUP is not supported on Windows. To opt out, disable the `HotReload` feature in the [Dapr application configuration]({{% ref "preview-features.md" %}}).
Copy link
Copy Markdown
Member

@msfussell msfussell May 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Since Dapr v1.18, changes to Resiliency resources are automatically detected and trigger a graceful restart of the Dapr sidecar (via SIGHUP) to apply the updated resiliency policies. Unchanged Resiliency resources are silently ignored. SIGHUP is not supported on Windows. To opt out, disable the `HotReload` feature in the [Dapr application configuration]({{% ref "preview-features.md" %}}).
Changes to Resiliency resources are automatically detected and trigger a graceful restart of the Dapr sidecar to apply the updated resiliency policies. Unchanged Resiliency resources are silently ignored.. To opt out, disable the `HotReload` feature in the [Dapr Resiliency]({{% ref "configuration-overview.md" %}}).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here. This has to be fixed for Windows. Cannot release otherwise.

## Hot Reloading

When the [`HotReload` feature gate]({{% ref "support-preview-features" %}}) is enabled, changes to Resiliency resources are automatically detected and trigger a graceful restart of the Dapr sidecar (via SIGHUP) to apply the updated resiliency policies. Unchanged Resiliency resources are silently ignored. SIGHUP is not supported on Windows.
Since Dapr v1.18, changes to Resiliency resources are automatically detected and trigger a graceful restart of the Dapr sidecar (via SIGHUP) to apply the updated resiliency policies. Unchanged Resiliency resources are silently ignored. SIGHUP is not supported on Windows. To opt out, disable the `HotReload` feature in the [Dapr application configuration]({{% ref "preview-features.md" %}}).
Copy link
Copy Markdown
Member

@msfussell msfussell May 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Since Dapr v1.18, changes to Resiliency resources are automatically detected and trigger a graceful restart of the Dapr sidecar (via SIGHUP) to apply the updated resiliency policies. Unchanged Resiliency resources are silently ignored. SIGHUP is not supported on Windows. To opt out, disable the `HotReload` feature in the [Dapr application configuration]({{% ref "preview-features.md" %}}).
Changes to Resiliency resources are automatically detected and trigger a graceful restart of the Dapr sidecar to apply the updated resiliency policies. To opt out, disable the `HotReload` feature in the [Dapr application configuration]({{% ref "configuration-overview.md" %}}).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to update the https://docs.dapr.io/operations/configuration/configuration-overview/ application configuration section to add the hot reload feature into the list and then reference it here.

@msfussell msfussell changed the title docs: graduate HotReload to GA docs: Graduate Component HotReloading to GA May 23, 2026
@msfussell msfussell added this to the v1.18 milestone May 23, 2026
Copy link
Copy Markdown
Member

@msfussell msfussell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed

### Configurations, Resiliency, and HTTPEndpoints

With the `HotReload` feature gate enabled, the Dapr sidecar also supports reloading [Configuration]({{% ref "configuration-overview.md" %}}), [Resiliency]({{% ref "resiliency-overview.md" %}}), and [HTTPEndpoint]({{% ref "service-invocation-overview.md" %}}) resources.
The Dapr sidecar also reloads [Configuration]({{% ref "configuration-overview.md" %}}), [Resiliency]({{% ref "resiliency-overview.md" %}}), and [HTTPEndpoint]({{% ref "service-invocation-overview.md" %}}) resources.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The Dapr sidecar also reloads [Configuration]({{% ref "configuration-overview.md" %}}), [Resiliency]({{% ref "resiliency-overview.md" %}}), and [HTTPEndpoint]({{% ref "service-invocation-overview.md" %}}) resources.
The Dapr sidecar also reloads [Configuration]({{% ref "configuration-overview.md" %}}), [Resiliency]({{% ref "resiliency-overview.md" %}}), WorkflowAccessPolicy({{% ref "workflow-access-policy.md" %}}) and [HTTPEndpoint]({{% ref "service-invocation-overview.md" %}}) resources.

Copy link
Copy Markdown
Contributor Author

@javier-aliaga javier-aliaga May 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@msfussell I cannot find the workflow-access-policy.md file, they are still pending to be merged https://github.com/dapr/docs/pull/5114/changes , I will add the reference but it will not work until the other one is merged

javier-aliaga and others added 3 commits May 25, 2026 10:22
kit uses a named pipe on Windows, so the SIGHUP-not-supported caveats
were misleading. Drop them.

Signed-off-by: Javier Aliaga <javier@diagrid.io>
Co-authored-by: Mark Fussell <markfussell@gmail.com>
Signed-off-by: Javier Aliaga <javier@diagrid.io>
Signed-off-by: Javier Aliaga <javier@diagrid.io>
@javier-aliaga javier-aliaga requested a review from msfussell May 26, 2026 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants