fix: Fix repeated 403 due to app namespace being undefined (#20699) (cherry-pick #20819) #20860
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.
Cherry-picked fix: Fix repeated 403 due to app namespace being undefined (#20699) (#20819)
Fixes #20699
Constructor may not get called every time the application changes, so previous this.appNamespace could be stale. But the update to use
this.props.match.params.appnamespace
could also fail if it's undefined.As a fix, create and use a helper function
getAppNamespace
which has a special case handling for undefined.Also, use a namespaced endpoint when namespace is not undefined.
It needs to be cherry-picked to v2.11-2.13.
Signed-off-by: Andrii Korotkov andrii.korotkov@verkada.com