please tell me this is not the only way to get CI with orynetwork 🤔

/usr/bin/expect <<'EOF'

spawn ory auth

expect "Do you want to sign in to an existing Ory Network account?"

send -- "y\r"

expect "Email:"

send -- "${{ inputs.username }}\r"

expect "Password:"

send -- "${{ inputs.password }}\r"

expect eof

EOF

Hey, right now it is 😬 There is also a github action, https://github.com/lomsa-dev/ory-cli-action but that does the same thing. We are working on a terraform provider and updates to the CLI however.

is the session information stored purely in memory of the cli? i can see that the tunnel is creating an api key.. can i somehow create my own and supply it to the cli?

@prehistoric-businessperson-29259 Not sure if the api token (PAT) is supported, but when you log in once, you get a session token stored in your home directory, in a hidden file called .ory-cloud.json. Nothing prevents you from distributing this 🙂. However, it will expire after x days, so you'll have to rotate it. That's not necessarily a bad thing in all regards, though!

Thanks @curved-fountain-46946 -- i wish I had read this 3 months ago 😭 -- i would have done some things differently. not sure how i missed that file! (i missed the message cus i didn't log back in 🙃 )