Skip to content

Deprecate StreamMicrogridDispatches RPC#351

Open
Marenz wants to merge 1 commit into
frequenz-floss:v1.x.xfrom
Marenz:split-hostdispatch
Open

Deprecate StreamMicrogridDispatches RPC#351
Marenz wants to merge 1 commit into
frequenz-floss:v1.x.xfrom
Marenz:split-hostdispatch

Conversation

@Marenz

@Marenz Marenz commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Deprecate the controller-facing StreamMicrogridDispatches RPC and its request/response messages instead of removing them.

This keeps the change non-breaking:

  • The RPC, its StreamMicrogridDispatchesRequest/StreamMicrogridDispatchesResponse messages, and the streaming event import are all retained.
  • Deprecation is expressed via option deprecated = true plus generic doc notes.
  • Existing clients keep working while documenting that this controller-facing part of the API will move out as part of a future Dispatch API split.

No specific target repository or replacement service is named here; the exact split shape is left unspecified for now.

@Marenz Marenz requested a review from a team as a code owner June 12, 2026 11:46
@Marenz Marenz requested review from stefan-brus-frequenz and removed request for a team June 12, 2026 11:46
@github-actions github-actions Bot added part:docs Affects the documentation part:protobuf Affects the protocol buffer definition files labels Jun 12, 2026
@llucax

llucax commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

What are we gaining by removing streaming from this API? It is a breaking change, what's the improvement here?

@Marenz

Marenz commented Jun 15, 2026

Copy link
Copy Markdown
Contributor Author

Streaming is controller-only and no public client uses it - Kuiper proxy and the etrading actor are both CRUD-only. Removing it just keeps the public API honest. But it's a breaking change for no functional gain, so I'm happy to keep it in the public API too - worth discussing whether the tidier surface is worth the break.

@llucax

llucax commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

We can deprecate it to make it clear the intention is to remove it in the future.

@Marenz Marenz force-pushed the split-hostdispatch branch from 7d11f0e to 2c1d9d2 Compare July 1, 2026 11:46
@Marenz Marenz changed the title Split StreamMicrogridDispatches into HostDispatch API Deprecate StreamMicrogridDispatches RPC Jul 1, 2026
Comment thread README.md Outdated
Comment on lines +23 to +28
> [!NOTE]
> Real-time dispatch streaming for controllers is moving to the dedicated
> [HostDispatch API](https://github.com/frequenz-io/frequenz-api-hostdispatch)
> (private, controller-only). The `StreamMicrogridDispatches` RPC in this API is
> deprecated and will be removed in a future major release. New controller-facing
> integrations should use `HostDispatchService`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This note makes no sense as it is...

Comment thread RELEASE_NOTES.md Outdated
and `StreamMicrogridDispatchesResponse` messages are now deprecated. Real-time
dispatch streaming for controllers is moving to the dedicated
`HostDispatchService` in the
[HostDispatch API](https://github.com/frequenz-io/frequenz-api-hostdispatch).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Same

@llucax llucax left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Well, actually the mention to the internal repo is everywhere. It makes no sense in a private repo, and we don't even know if we are going this way, so I would just remove all mentions to it and just mention the API will be split for now without any further precision.

Mark the controller-facing stream RPC and its request/response messages as deprecated instead of adding or removing service surface. This keeps the change non-breaking while documenting that this part of the API will move out in a future Dispatch API split.

Signed-off-by: Mathias L. Baumann <mathias.baumann@frequenz.com>
@Marenz Marenz force-pushed the split-hostdispatch branch from 2c1d9d2 to 0700309 Compare July 1, 2026 13:18

@llucax llucax left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We should only do this once we know exactly where are we moving it, so I would wait on this too for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

part:docs Affects the documentation part:protobuf Affects the protocol buffer definition files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants