fix(multitenancy): consistently use tenant nomenclature everywhere #6389
+111
−43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of Change
Description
This fixes the inconsistent nomenclature used for tenants in router and drainer code
Additional Changes
Motivation and Context
This will eradicate confusion between
name
andtenant_id
names in the tenant config. In the config belowpublic = { base_url = "http://localhost:8080/", schema = "public", redis_key_prefix = "", clickhouse_database = "default"}
The key
public
will be the tenant_id. This PR adds a custom deserializer for this partHow did you test it?
This cannot be tested on sandbox without enabling Multi Tenancy
x-tenant-id
It should return 200 and
tenant-id
should be the which has been passedtenant-id
, It should return an errorChecklist
cargo +nightly fmt --all
cargo clippy