Chore: Check for Cloud client secret to check if workspace is registered #27229
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.
Proposed changes (including videos or screenshots)
The main change of this PR is to consider a workspace registered only if it has both
Cloud_Workspace_Client_IdandCloud_Workspace_Client_Secretsettings saved on the server's cache here.The problem was it was checking only for
Cloud_Workspace_Client_Idbut was also using the secret to perform requests afterwards, and due to some race conditions on how settings are saved in cache, it was happening some times theclientIdwas in cache but the secret was not, so now with this additional check it will prevent those cases.The other changes are due to TS conversion.
Issue(s)
ARCH-84
Steps to test or reproduce
Further comments