Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: local event producer #243

Merged
merged 1 commit into from
May 15, 2024
Merged

build: local event producer #243

merged 1 commit into from
May 15, 2024

Conversation

iloveagent57
Copy link
Contributor

@iloveagent57 iloveagent57 commented May 14, 2024

Description

Requires openedx/enterprise-access#468.

Installs openedx-events, kafka, and so forth for local development of kafka events. Upgrades deps due to installation of events packages. Provides example of brining the kafka broker up and producing a test/ping event.
ENT-8761

See the additions to the README for how to test this locally.

Merge checklist

  • All reviewers approved
  • CI build is green
  • Documentation updated (not only docstrings)
  • Commits are squashed

@iloveagent57 iloveagent57 force-pushed the aed/local-events branch 2 times, most recently from fc539dd to 6f38279 Compare May 14, 2024 14:18
@iloveagent57 iloveagent57 changed the title feat: wip build of local event producer build: local event producer May 14, 2024
Install event-bus packages for local usage.
Adds a `produce_enterprise_ping_event` mgmt command
for local testing/demos of interservice event pub-sub.
ENT-8761
Comment on lines +41 to +47
# Define a Signal with the type (unique name) of the event to process,
# and tell it about the expected schema of event data. The producer of our ping events
# should emit an identical signal (same event_type and data schema).
ENTERPRISE_PING_SIGNAL = OpenEdxPublicSignal(
event_type="org.openedx.enterprise.core.ping.v1",
data=ENTERPRISE_PING_DATA_SCHEMA
)
Copy link
Contributor

Choose a reason for hiding this comment

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

Are we going to define more than a small base set of signals in every repo, or is the idea they can be defined DRY in a shared repo?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

These signals are really for demo/testing purposes - our production-use signals will be defined in openedx-events: openedx/openedx-events#347

@iloveagent57 iloveagent57 merged commit 55d3025 into main May 15, 2024
8 checks passed
@iloveagent57 iloveagent57 deleted the aed/local-events branch May 15, 2024 14:09
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