nice-musician-60677
07/25/2024, 2:01 PMdocker run --rm -p 62100:62100 -e ORY_PROJECT_API_KEY=ory_pat_xxx oryd/ory tunnel --port 62100 --project suspicious-wozniak-by8qc6gqla http://localhost:42100
Side note: I can pass in whatever I want for the ORY_PROJECT_API_KEY, even when using a wrong key, it will not complain. But when using it with the ORY_WORKSPACE_API_KEY, it will actually complain when using a wrong key. But still, when using the correct key, I'm not authenticated and I will receive the browser URL. I also tried adding the --quiet flag, but this will get me: please authenticate the CLI or remove the --quiet flag - Am I doing anything wrong?steep-lamp-91158
nice-musician-60677
07/25/2024, 2:15 PMdocker run --rm -p 62100:62100 -e ORY_PROJECT_API_KEY=xxx -e ORY_WORKSPACE_API_KEY=xxx oryd/ory tunnel --port 62100 --project suspicious-wozniak-by8qc6gqla --workspace xxx http://localhost:42100
But the behaviour is the same, I'm getting the browser URL prompt.microscopic-painter-84459
07/25/2024, 3:03 PM0.3.4) was removed from homebrew so users are now downloading an unstable prerelease version by default without any mention of it in the CLI documentation. 0.3.4 can still be downloaded as binary, but I think defaulting to that and removing the prior from brew like that is pretty rough.steep-lamp-91158
steep-lamp-91158
microscopic-painter-84459
07/25/2024, 3:05 PMmicroscopic-painter-84459
07/25/2024, 3:07 PMsteep-lamp-91158
nice-musician-60677
07/25/2024, 3:41 PMsteep-lamp-91158
nice-musician-60677
07/25/2024, 3:48 PMnice-musician-60677
07/25/2024, 4:50 PMbash <(curl -s https://raw.githubusercontent.com/ory/meta/master/install.sh) -b . ory v0.3.4nice-musician-60677
07/26/2024, 8:33 AMlimited-photographer-61008
07/26/2024, 1:32 PM--quiet. For now we've pinned to v0.3.4.steep-lamp-91158
nice-musician-60677
07/26/2024, 11:28 PMsteep-lamp-91158
--config flag help for details.steep-lamp-91158
nice-musician-60677
07/30/2024, 1:11 PM--quiet flag). But (at least for starting the tunnel) it is necessary to add both API keys as well as the --workspace flag. If I only use the ORY_PROJECT_API_KEY it will not work. Is it meant to be like this? In the migration guide it says that "Depending on the use-case you might need to use one or both.", so maybe starting the tunnel is one of these use-cases?steep-lamp-91158
nice-musician-60677
07/30/2024, 1:16 PM--project flag to pass the slug? This one is actually also required for me 😄 I need to set both API-keys, the --project and the --workspace flag to make it work currently.steep-lamp-91158
ory tunnel --project 23a2e --workspace 'My workspace name prefix'
So we first need to list workspaces, then list projects of the correct workspace, and then we get the slug of the project.nice-musician-60677
07/30/2024, 1:28 PM--project flag, but for the --workspace flag I cannot use the name of the workspace. It really has to be that long UUID.steep-lamp-91158
steep-lamp-91158
steep-lamp-91158
nice-musician-60677
07/30/2024, 1:34 PMsteep-lamp-91158
limited-photographer-61008
07/31/2024, 11:52 AMWe are using the oryd/ory docker image in our local compose setup where we use the ory tunnel feature to bootstrap our environment.This is similar to our use case. We automatically start the tunnel when a dev starts our API service in their dev environment. Every dev has their own project, so we are not worried about revoking access.
limited-photographer-61008
07/31/2024, 11:53 AM--workspace if the project isn't in a workspace?steep-lamp-91158