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

Support namespaces/domains/multi-tenancy #169

Open
saig0 opened this issue Sep 23, 2021 · 0 comments
Open

Support namespaces/domains/multi-tenancy #169

saig0 opened this issue Sep 23, 2021 · 0 comments
Labels
enhancement New feature or request hacktoberfest

Comments

@saig0
Copy link
Contributor

saig0 commented Sep 23, 2021

In order to support different namespaces/domains (i.e. multi-tenancy), we need a way to store the data based on the namespace and be able to query by the namespace This can be useful to collect data from multiple environments (e.g. dev/stage/prod) by a single consumer, especially, for building a testing tool and running multiple test cases.

Each data entity (e.g. processes, process instances, jobs, etc.) contains a new field for the namespace.

The importer sets the namespace when reading exported records.

The GraphQL queries contain an optional field to filter by the namespace.

Related to/depends on camunda-community-hub/zeebe-hazelcast-exporter#132.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request hacktoberfest
Projects
None yet
Development

No branches or pull requests

1 participant