Preserve explicit workspace in IDE device login#212
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Root cause
The device-flow branch cleared OPSDEV_USERNAME before checking the positional . This prevented stale persisted state from being forwarded, but it also discarded a workspace explicitly supplied by the user. In addition, the nested CLI process reloads persisted config, so environment-only clearing cannot reliably express whether a workspace was intentional.
The task now invokes the CLI with no positional user for implicit device login and with the positional user when one was explicitly selected. The companion CLI fix gives this argument precedence over persisted environment values.
Companion PR: apache/openserverless-cli#42
Validation
The admin-api authenticated-namespace mismatch check is not changed or bypassed.