Skip to content

Conversation

avishniakov
Copy link
Contributor

@avishniakov avishniakov commented Apr 24, 2024

Describe changes

ZenML can run with new dashboard by default!
Switch to old is still supported either with Server Config (env ZEN_SERVER_USE_LEGACY_DASHBOARD) or with --legacy flag of zenml up.

  • Rework dashboard install script to pull 2 artifacts for legacy and new dashboards (currently hard fixed to v0.17.0-rc1, we will switch to latest after testing)
  • Add --legacy flag to zenml up to run the old dashboard
  • Add use_legacy_dashboard server config option, defaulted to False => new dashboard is default one
  • Extended CSP to support the What's New feature of the new dashboard
  • Added ZEN_SERVER_USE_LEGACY_DASHBOARD env
  • Update URL building logic of dashboard utils
  • Updated deployment config to support dashboard switches
  • Update Server API to support also new dashboard file structure

Docs update will follow separately

Pre-requisites

Please ensure you have done the following:

  • I have read the CONTRIBUTING.md document.
  • If my change requires a change to docs, I have updated the documentation accordingly.
  • 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.
  • If my changes require changes to the dashboard, these changes are communicated/requested.

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)

Summary by CodeRabbit

  • New Features

    • Added support for launching the legacy ZenML dashboard via a new --legacy option.
    • Introduced configuration options to toggle between the legacy and new dashboard versions.
  • Enhancements

    • Updated the installation script to handle different releases of the ZenML Dashboard dynamically.
    • Enhanced server deployment configurations to support environment-specific dashboard settings.
  • Documentation

    • Updated internal documentation to reflect changes in dashboard management and deployment strategies.

@github-actions github-actions bot added the internal To filter out internal PRs and issues label Apr 24, 2024
@github-actions github-actions bot added the enhancement New feature or request label Apr 24, 2024
Copy link
Contributor

coderabbitai bot commented Apr 24, 2024

Important

Auto 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.

Walkthrough

The updates across various files introduce support for a legacy version of the ZenML Dashboard, enabling users to choose between the new and legacy versions. These changes involve adding configuration parameters, environment variables, and conditional logic to facilitate backward compatibility and user flexibility in selecting the dashboard version.

Changes

File Path Change Summary
scripts/install-dashboard.sh Updated to handle different releases of the ZenML Dashboard, including fetching and installing specified versions.
src/zenml/cli/server.py
src/zenml/config/server_config.py
src/zenml/constants.py
src/zenml/models/v2/misc/server_models.py
Added support for a --legacy option and configuration parameters to toggle the legacy dashboard.
src/zenml/utils/dashboard_utils.py Enhanced URL handling logic to support legacy dashboard based on configuration.
src/zenml/zen_server/.../docker_zen_server.py
src/zenml/zen_server/.../local_zen_server.py
src/zenml/zen_server/zen_server_api.py
src/zenml/zen_stores/base_zen_store.py
Handling of environment variables and serving logic for legacy dashboard across different server deployment and store configurations.

Poem

🐇💻✨
In the fields of code, where the data streams flow,
The rabbits tweaked dashboards, with old and new glow.
Legacy and latest, side by side they sit,
A toggle, a switch, for whichever you fit.
Hop through the changes, with ease and fun,
For with every update, new victories are won! 🎉🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
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>.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

@avishniakov
Copy link
Contributor Author

@coderabbitai review

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 7

@avishniakov
Copy link
Contributor Author

@coderabbitai review

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

Out of diff range and nitpick comments (4)
scripts/install-dashboard.sh (4)

8-8: Ensure consistency in variable naming for clarity.

Consider renaming LEGACY_INSTALL_DIR to INSTALL_DIR_LEGACY to maintain consistency with INSTALL_DIR.


5-11: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [10-18]

Improve user guidance in error messages.

Consider providing more specific guidance on how to install missing tools or disable checksum verification in the error messages.


32-33: Clarify the error message for better user understanding.

Consider specifying which exact directory entries need to be removed from the .gitignore file in the error message.


105-105: Enhance error messaging for checksum verification failure.

Consider providing suggestions on what to do next or how to troubleshoot when the checksum verification fails.

@avishniakov avishniakov changed the title [WIP] Support New Dashboard release Support New Dashboard release Apr 29, 2024
Copy link
Contributor

@strickvl strickvl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@avishniakov
Copy link
Contributor Author

Not waiting for MacOS tests, since they will fail, as expected - fix is happening on another branch.

@avishniakov avishniakov merged commit 5ec22e4 into develop Apr 29, 2024
@avishniakov avishniakov deleted the feature/OSSK-526-support-oss-dashboard-release branch April 29, 2024 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request internal To filter out internal PRs and issues run-slow-ci
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants