feat(ops): allow disabled entities for storage sets that are not in use #3572
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.
Add a new config that lets us disable entity loading when we want to disable storage sets temporarily.
We want to remove the
cdc
andsessions
storage sets for ops changes, but that causes the validation on EntityFactory loading to faileven if the dataset is in
DISABLED_DATASETS
. This is because initialize_snuba is loading entities first:snuba/snuba/core/initialize.py
Lines 32 to 43 in afcfb2a
snuba/snuba/datasets/entities/factory.py
Lines 67 to 72 in a6a41ef
I tested locally that with the relevant entities disabled we can remove the storage sets
cdc
andsessions
andsnuba api
will start without the above error