RHOAIENG-14811 The userdID was not correctly transferred to the frontend #3387
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.
Closes https://issues.redhat.com/browse/RHOAIENG-14811
We now get the userID from the status api endpoint if set.
This builds on RHOAIENG-9480/PR #3107.
This closes the first try in #3362
Description
The previous code did not correctly pass the userID from the backend around in the frontend.
The backend already has it correctly on a 2.14 cluster and provides it via /api/status call.
How Has This Been Tested?
Manual test in dev-mode running
npm run start:dev:ext
against an instance on Dev-Sandbox and a non-Sandbox one.Then looking at the console output for the the Identify event
If the userID looks like this (whith chars) it is an anonymous one. If it is numeric (may be negative) and short (probably < 8 digits), then it is a web-user-id.
Request review criteria:
Self checklist (all need to be checked):
After the PR is posted & before it merges:
main
cc @andrewballantyne