Skip to content
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.

Add another configuration map for data residency configuration #1680

Closed
zhongduo opened this issue Sep 10, 2020 · 0 comments · Fixed by #1681
Closed

Add another configuration map for data residency configuration #1680

zhongduo opened this issue Sep 10, 2020 · 0 comments · Fixed by #1681
Assignees
Labels
area/broker area/sources kind/feature-request New feature or request priority/1 Blocks current release defined by release/* label or blocks current milestone
Milestone

Comments

@zhongduo
Copy link
Contributor

Problem
This configuration will be used to support #1678. But since the data residency itself is small, here are two possible ways:

  1. create one for generic configuration in eventing so that new configurations can be added.
  2. create one for data residency only.

Persona:
Which persona is this feature for?

Exit Criteria
A new config map in clound-run-events namespace.

Time Estimate (optional):
How many developer-days do you think this may take to resolve?

Additional context (optional)
Add any other context about the feature request here.

@zhongduo zhongduo added the kind/feature-request New feature or request label Sep 10, 2020
@zhongduo zhongduo self-assigned this Sep 10, 2020
@grantr grantr added priority/1 Blocks current release defined by release/* label or blocks current milestone area/broker area/sources labels Sep 14, 2020
@grantr grantr added this to the Backlog milestone Sep 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/broker area/sources kind/feature-request New feature or request priority/1 Blocks current release defined by release/* label or blocks current milestone
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants