DUPLO-26089: use a predetermined localPort #29
Merged
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.
Overview
Proposed by Ofir @ Seven AI
duplo-jit
to have it use a predetermined localPort, which could then be exposed from devcontainerSlack:
question for the duplo folks about duplo-jit + aws + admin access
specifically, this part of the ~/.aws/config file:
some of our team is working within a visual studio devcontainer , so when duplo-jit sends us out to the browser to click "Authorize" , the authorize button won't work because the localPort isn't exposed from our devcontainer
example url: https://duplo.cloud.sevenai.com/app/user/verify-token?localAppName=duplo-jit&localPort=45461&isAdmin=true
what is the recommended solution ? I believe Ofir was hacking around on duplo-jit to have it use a predetermined localPort, which could then be exposed from devcontainer, in case that helps