Run tunnel with Go SDK

[weeco]

Preflight checklist

• [X] I could not find a solution in the existing issues, docs, nor discussions.
• [X] I agree to follow this project's Code of Conduct.
• [X] I have read and am following this repository's Contribution Guidelines.
• [X] This issue affects my Ory Network project.
• [X] I have joined the Ory Community Slack.
• [ ] I am signed up to the Ory Security Patch Newsletter.

Describe your problem

I got started with the Ory network and looked into new ways of solving authentication (and authorization) for my projects. Ory looked promising, but in the end we decided against using Ory because running the tunnel with a separate CLI on every dev environment as well as on integration environments seemed like a bad developer experience due to the additional requirements.

Describe your ideal solution

Instead of requiring a separate CLI to be installed that then runs the tunnel, this should be part of the Go SDK, so that you just have a single Go application where you can optionally run the tunnel as well.

Workarounds or alternatives

• Adding the CLI as part of our Docker image
• Add taskfiles to streamline the experience for other devs who need to install and run the ORY tunnel

Version

v1.1.41

Additional Context

No response

[github-actions[bot]]

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

• open a PR referencing and resolving the issue;
• leave a comment on it and discuss ideas on how you could contribute towards resolving it;
• leave a comment and describe in detail why this issue is critical for your use case;
• open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

[aeneasr]

I think this is a good idea, but supporting different programming languages well will be a lot of effort.