Skip to content

feat: add HotCVEOnFinishedMessageTypeProp constant#103

Merged
kooomix merged 1 commit into
mainfrom
feat/hot-cve-message-type-prop
Apr 20, 2026
Merged

feat: add HotCVEOnFinishedMessageTypeProp constant#103
kooomix merged 1 commit into
mainfrom
feat/hot-cve-message-type-prop

Conversation

@kooomix
Copy link
Copy Markdown
Contributor

@kooomix kooomix commented Apr 20, 2026

Used as MsgPropMessageType value when publishing HotCVEOnFinishedMessage to k8s-objects-finished-v1 topic. UNS uses this to route messages to the hot CVE notification handler.

Summary by CodeRabbit

  • Chores
    • Enhanced backend infrastructure to improve notification message handling capabilities for the vulnerability management system, including better support for tracking notification completion events.

Used as MsgPropMessageType value when publishing HotCVEOnFinishedMessage
to k8s-objects-finished-v1 topic. UNS uses this to route messages to
the hot CVE notification handler.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 20, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0a865370-be20-4d21-a534-f6c42a47a256

📥 Commits

Reviewing files that changed from the base of the PR and between e2c80ac and cd52bbc.

📒 Files selected for processing (1)
  • pulsar/common/topics.go

📝 Walkthrough

Walkthrough

A new exported constant HotCVEOnFinishedMessageTypeProp was added to define the message type property for hot CVE on-finish messages in the k8s-objects-finished-v1 topic. Minor formatting adjustments were made to adjacent hot CVE topic constants without changing their values.

Changes

Cohort / File(s) Summary
Hot CVE Message Type Property
pulsar/common/topics.go
Added constant HotCVEOnFinishedMessageTypeProp = "HotCVEOnFinished" for use as MsgPropMessageType property value; formatted spacing around related hot CVE topic constants.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested reviewers

  • matthyx

Poem

🐰 A hop, a skip, a constant new,
For CVE messages hot and true,
With spacing neat and values clear,
The hot-fix hops throughout the year! 🌟

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/hot-cve-message-type-prop

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@kooomix kooomix merged commit be189a0 into main Apr 20, 2026
5 of 6 checks passed
@github-actions
Copy link
Copy Markdown

Summary:

  • License scan: failure
  • Credentials scan: skipped
  • Vulnerabilities scan: skipped
  • Unit test: success
  • Go linting: success

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