Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document the programmatic API access options #3352

Merged
merged 8 commits into from
Feb 7, 2025

Conversation

stefannica
Copy link
Contributor

@stefannica stefannica commented Feb 6, 2025

Describe changes

Add documentation describing the various methods a user has to access the ZenML Pro API, ZenML Pro Tenant API and ZenML OSS Server API programmatically.

Also updates the ZenML Pro on-prem deployment guide to fix formatting and add upgrade/update instructions.

Rendered here:

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)

@stefannica stefannica requested a review from bcdurak February 6, 2025 15:50
Copy link
Contributor

coderabbitai bot commented Feb 6, 2025

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.


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>, please review it.
    • 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 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 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.
    • @coderabbitai help me debug CodeRabbit configuration file.

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. (Beta)
  • @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.

@github-actions github-actions bot added the internal To filter out internal PRs and issues label Feb 6, 2025
Copy link
Contributor

github-actions bot commented Feb 6, 2025

Images automagically compressed by Calibre's image-actions

Compression reduced images by 38.1%, saving 329.27 KB.

Filename Before After Improvement Visual comparison
docs/book/.gitbook/assets/vertexai_experiment_tracker_tb.png 303.66 KB 166.49 KB -45.2% View diff
docs/book/.gitbook/assets/vertexai_experiment_tracker_ui.png 180.03 KB 92.01 KB -48.9% View diff
docs/book/.gitbook/assets/zenml-oss-api-token-01.png 94.97 KB 76.80 KB -19.1% View diff
docs/book/.gitbook/assets/zenml-oss-api-token-02.png 101.34 KB 68.35 KB -32.6% View diff
docs/book/.gitbook/assets/zenml-pro-api-token-01.png 70.79 KB 57.35 KB -19.0% View diff
docs/book/.gitbook/assets/zenml-pro-api-token-02.png 112.47 KB 72.99 KB -35.1% View diff

387 images did not require optimisation.

Update required: Update image-actions configuration to the latest version before 1/1/21. See README for instructions.

@stefannica stefannica added the documentation Improvements or additions to documentation label Feb 6, 2025
@stefannica stefannica force-pushed the doc/document-api-tokens branch from 0f93b01 to e1a67df Compare February 6, 2025 17:12
@stefannica stefannica force-pushed the doc/document-api-tokens branch from e1a67df to 1b04f72 Compare February 6, 2025 17:16
@stefannica stefannica force-pushed the doc/document-api-tokens branch from b6c700e to 2f6f889 Compare February 6, 2025 17:37
Co-authored-by: Barış Can Durak <[email protected]>
Copy link
Contributor

@bcdurak bcdurak left a comment

Choose a reason for hiding this comment

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

🦭

@stefannica stefannica force-pushed the doc/document-api-tokens branch 7 times, most recently from 733d8e1 to 228dfd4 Compare February 7, 2025 15:51
@stefannica stefannica force-pushed the doc/document-api-tokens branch from 228dfd4 to 1e2f9ef Compare February 7, 2025 15:54
@stefannica stefannica merged commit 8efa744 into develop Feb 7, 2025
11 checks passed
@stefannica stefannica deleted the doc/document-api-tokens branch February 7, 2025 15:54
stefannica added a commit that referenced this pull request Feb 7, 2025
* Document the programmatic API access options

* Optimised images with calibre/image-actions

* Fix the formatting in the on-prem deployment page

* Add upgrade/update instructions for on-prem deployments

* Fix formatting again

* Apply suggestions from code review

Co-authored-by: Barış Can Durak <[email protected]>

* Fix indentation and page descriptions

* Fix indentation

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Barış Can Durak <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation internal To filter out internal PRs and issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants