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

Determine configuration strategy for new events #265

Open
1 task
rgraber opened this issue Sep 14, 2023 · 1 comment
Open
1 task

Determine configuration strategy for new events #265

rgraber opened this issue Sep 14, 2023 · 1 comment
Labels
event-bus Work related to the Event Bus.

Comments

@rgraber
Copy link
Contributor

rgraber commented Sep 14, 2023

A/C

  • An ADR detailing how new events will be rolled out to the community

Since #249, new events can be added to the event bus via configuration only (no code changes). Some options for how we would roll out new events:

  1. All events are off by default. New events are added to the configuration map in the producing service's configuration file with enabled=False so people know what events are available
  2. All events are on by default. New events are added to the configuration map in the config with enabled=True
  3. All new events start disabled by default, but are updated to be enabled by default as part of a planned release (with the change noted in the release notes)
@robrap robrap added the event-bus Work related to the Event Bus. label Sep 14, 2023
@robrap
Copy link
Contributor

robrap commented Sep 14, 2023

Note: Option 3 uses enabled as a temporary rollout toggle. If we use this route (which I like), we'd need to also understand how to get the best of https://edx.readthedocs.io/projects/edx-toggles/en/latest/how_to/documenting_new_feature_toggles.html. Or, maybe we should quite literally be using the toggle annotations for each of these?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
event-bus Work related to the Event Bus.
Projects
None yet
Development

No branches or pull requests

2 participants