Extract GitOps SSE handlers into dedicated stream module#19148
Conversation
✅ Deploy Preview for kubestellarconsole canceled.
|
|
👋 Hey @Copilot — thanks for opening this PR!
This is an automated message. |
Signed-off-by: GitHub <noreply@github.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits. 📝 Please follow instructions in the contributing guide to update your commits with the DCO Full details of the Developer Certificate of Origin can be found at developercertificate.org. The list of commits missing DCO signoff: DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
📌 Fixes
Issue linking is handled automatically by the system.
📝 Summary of Changes
SSE endpoint control flow for GitOps operators/subscriptions/helm releases was co-located with list/query code in
operators.go, increasing file coupling. This PR isolates stream-specific behavior into a focused stream file while preserving endpoint behavior and signatures.SSE extraction
StreamOperators,StreamOperatorSubscriptions, andStreamHelmReleasesout ofpkg/api/handlers/gitops/operators.gopkg/api/handlers/gitops/gitops_operator_streams.goas the stream-focused home for SSE handlersStream helper co-location
getDemoOperatorsForStreaminggetDemoHelmReleasesForStreamingSeparation of concerns
operators.gonow retains list/query/fetch/cache logicChanges Made
gitops_operator_streams.goChecklist
Please ensure the following before submitting your PR:
git commit -s)Screenshots or Logs (if applicable)
N/A (backend handler refactor only)
👀 Reviewer Notes
Please review for architectural separation only: stream endpoint behavior, event shapes, and handler signatures are intended to remain unchanged.