Fixing WATCH_NAMESPACE env variable handling for single namespace value #2606
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.
Signed-off-by: dhaja [email protected]
Description:
As mentioned in the linked issue, the
WATCH_NAMESPACE
has no effect in case there is no comma in it (single namespace value).Fixing this by adding entries in the
namespaces
map when theWATCH_NAMESPACE
is set and disregarding if it has commas in it or not.Link to tracking Issue: #2589
Testing:
Ran tests locally, verified in a kind cluster that namespaces map contains one item in case
WATCH_NAMESPACE
set and no comma in it, and multiple items if the env variable has comma-separated namespaces.Documentation:
N/A