Dynamic storage provider add aliases #4307
Merged
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.
This PR solves the problem we found yesterday where it is impossible to resolve storage ids like:
eoshome-a
, as those are aliases of real storage ids likeeoshome-i01
.We add a new section in the registry config:
And when the storage registry is passed a
storage_id
to find its providers, it will ensure if the givenstorage_id
is an alias, it will be resolved.Fixes #4303