Interactive project selection

[hperl]

Preflight checklist

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

Describe your problem

Many Ory CLI commands take a --project flag, e.g. ory update relation-tuples --project <id>. Usually, I need to do ory list projects first to get the project id, then invoke the command that takes the project. This is cumbersome.

Describe your ideal solution

If I don't specify the project via the --project flag, instead of an error message I want a dropdown / select screen that helps me choose the project and then continues with the command.

Example:

$ ory update relation-tuples

> Someproject (slug: foo-bar-123)
  Someotherproject (slug: bar-baz-456)

↑/↓ to navigate, ⏎ to select

Workarounds or alternatives

Leave as is.

Version

master/HEAD

Additional Context

• For non-interactive use, we should add a new --non-interactive flag and NON_INTERACTIVE environment variable that disables the interactive features.
• https://github.com/charmbracelet/bubbletea is a nice library that helps building interactive terminal UIs and that already does the heavy-lifting for us.

[github-actions]

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 🙏✌️