Hardcoded "TODO" subject in CloudEvents NATS driver

[Amit-Matth]

Describe the issue

Summary

In the NATS eventing driver (internal/events/nats/natschannel.go), the subject field for outgoing CloudEvents is currently hardcoded to the literal string "TODO". This field should instead uniquely identify the specific entity (such as a repository, project, or artifact) that the event is about.

Impact

• Event Filtering: NATS JetStream relies on subjects for efficient event routing and filtering. Hardcoding the subject to "TODO" makes it impossible for consumers to efficiently filter events.
• Spec Compliance: It violates the CloudEvents specification, which expects the subject to refer to a specific resource.

To Reproduce

1. Open the file internal/events/nats/natschannel.go.
2. Locate the sendEvent function (around line 203).
3. Observe line 209: event.SetSubject("TODO").
4. Note the developer comment: // This *should* represent the entity, but we don't have a standard field for it yet.

What version are you using?

Latest main branch (v0.1.0)

[Deepesh123455]

Hey folks, I've been looking into this bug. I have a working fix locally that replaces the hardcoded TODO subject with the actual entity identifier, and all tests are passing. I will open a PR from my fork shortly so you can review the approach!

[TRIVENI206]

Hi! I noticed a previous PR attempted to address this issue but was closed due to mixing refactoring with the behavioral change.

I’d like to work on this by focusing on a minimal fix—deriving the CloudEvents subject from existing metadata without introducing additional refactoring, to keep the change easy to review.

Please let me know if this approach sounds good, and if the issue is still available to take up. Thanks!

[Deepesh123455]

Hey @TRIVENI206, go for it! I was trying to do a broader refactor, but if you want to tackle the minimal fix, feel free to take this issue.