-
-
Notifications
You must be signed in to change notification settings - Fork 22
-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot auto confirm the social sign in prompt on tunnel run #219
Comments
|
Okay nice. Shouldn't we maybe update the cli to be more descriptive? For instance when running: ➜ ~ ory tunnel -h
...
Flags:
--allowed-cors-origins strings A list of allowed CORS origins. Wildcards are allowed.
-c, --config string Path to the Ory Cloud configuration file.
--cookie-domain string Set a dedicated cookie domain.
--debug Use this flag to debug, for example, CORS requests.
--default-redirect-url string Set the URL to redirect to per default after e.g. login or account creation.
--dev Use this flag when developing locally.
-h, --help help for tunnel
--port int The port the proxy should listen on. (default 4000)
--project string The slug of your Ory Cloud Project.
-q, --quiet Be quiet with output printing.
-y, --yes Confirm all dialogs with yes. We can se the |
Yeah true, we should update the description a bit. Something like "Surpresses all dialogues and answers with the default". Contribs welcomed :) |
Preflight checklist
Describe the bug
The Ory tunnel will now prompt the user about using the social sign in option like so:
When using the flag
--yes
or-y
on the command it doesn't confirm it and continue.Reproducing the bug
Run
ory tunnel
for the first time and the prompt will appear. Try skip it by adding the--yes
flag:Relevant log output
No response
Relevant configuration
No response
Version
v0.1.41
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Ory Cloud
Additional Context
Reported on slack:
https://ory-community.slack.com/archives/C010F7Z4XM1/p1663858573933829
Right now a workaround could be for the user to pipe in the confirmation themselves:
sh -c "yes | ory tunnel http://localhost:3000/ --project <project-slug> --dev"
The text was updated successfully, but these errors were encountered: