Repository navigation
RHIDP-17796: [Signals-Frontend] Update and Expand Product Documentation for GA - #2661
Conversation
PR Build ResultsBuild passed -- 38/38 titles | 128s Content Quality AssessmentCQA Report
SummaryChecks: 22 total, 22 pass, 0 fail Modules not yet in product_product61 modules (proc, con, ref) are not yet included in the
|
e2fc30c to
3481cf4
Compare
ciiay
left a comment
There was a problem hiding this comment.
Technical review
LGTM for Signals GA documentation.
- Correctly describes Signals as an enabling plugin (no UI of its own), with Notifications as the primary consumer
- GA support note is clear and does not imply Notifications is GA
- Points to the generated plugin support tables for status
- Enable procedure covers both frontend and backend packages and preserves the existing anchor
One ask before merge: please clarify (or remove) the optional events.http.topics: [signals] step. That config is for Events HTTP ingress (/api/events/http/signals), not something required for the usual Notifications → Signals real-time path. As written, admins enabling Signals for notifications may think they need it.
525bddb to
b08e8b9
Compare
pabel-rh
left a comment
There was a problem hiding this comment.
Approved with some comments.
Document the Signals plugin for GA as an enabling plugin (no UI of its own), with Notifications as the primary consumer. Add the enable procedure covering both frontend and backend packages, and map the content into the JTBD navigation. Clarify that the optional events.http.topics: [signals] step configures the Events HTTP ingress endpoint (/api/events/http/signals) for external systems, and is not required for real-time notification delivery.
b08e8b9 to
8643f37
Compare
|



IMPORTANT: Do Not Merge - To be merged by Docs Team Only
Version(s): 2.1
Issue: RHIDP-17796
Preview: