New zenml login and CLI style improvements

[znegrin]

Describe changes

I implemented an interactive login menu for the zenml login command to achieve a better user experience by providing clear login options instead of automatically defaulting to ZenML Pro.
When users run zenml login without arguments, they now see a styled interactive menu with three options:

1. Login to a local server (zenml login --local)
2. Login to ZenML Pro (https://cloud.zenml.io)
3. Login to a custom cloud server (prompts for URL)

This also includes CLI styling improvements across multiple files for better visual consistency and remove unnecessary colors to make it more legible.

Pre-requisites

Please ensure you have done the following:

• I have read the CONTRIBUTING.md document.
• I have added tests to cover my changes.
• I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
• IMPORTANT: I made sure that my changes are reflected properly in the following resources:
  • ZenML Docs
  • Dashboard: Needs to be communicated to the frontend team.
  • Templates: Might need adjustments (that are not reflected in the template tests) in case of non-breaking changes and deprecations.
  • Projects: Depending on the version dependencies, different projects might get affected.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (add details above)

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[htahir1]

One case not handled is if you do zenml login once and authenticate through ZenML Pro, then do zenml login again it doesnt show the questionnaire anymore. Is this what we want?

The underlying reason is that zenml login is also used to switch around between workspaces once authenticated to pro organization

so you can do: zenml login internal and zenml login demo-tenant to switch between workspaces.

[znegrin]

One case not handled is if you do zenml login once and authenticate through ZenML Pro, then do zenml login again it doesnt show the questionnaire anymore. Is this what we want?

Right now how it works is that if you do zenml login again and you are already logged to ZenML Pro, it goes automatically to the selection screen again, which kind of makes sense as it is the expected behavior to switch to a new workspace, right?

[htahir1]

ok i agree. left some more comments

[htahir1]

For me this looks good. but now we need @bcdurak to take a look too

[htahir1]

Closes #3791

[znegrin]

@bcdurak @htahir1 @schustmi I think I covered all the issues and also passed the scripts for the tests. I hope it is all ok now. Please let me know if there's something else I can fix or do in a better way, as I am more used to work with frontend stuff, and it is my first time working on changes for a CLI interface. Thank you!