Skip to content

Conversation

@stefannica
Copy link
Contributor

Describe changes

Document ZenML Pro Personal Access Tokens and deprecate API tokens.

This PR also removes the recently introduced zenml token CLI command.

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 htahir1 November 5, 2025 10:07
@github-actions
Copy link
Contributor

github-actions bot commented Nov 5, 2025

✅ No broken links found!

@github-actions github-actions bot added internal To filter out internal PRs and issues enhancement New feature or request labels Nov 5, 2025
Copy link
Contributor

@htahir1 htahir1 left a comment

Choose a reason for hiding this comment

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

One comment for now. Also can you give me the final URL that i can use in the dashboard? i need something to link from the zenml cloud dashboard to the docs page that described the PAT

Copy link
Contributor

Choose a reason for hiding this comment

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

I am wondering, whether it makes sense to add a page here in the main Documentation space and call it "with a PAT" and thne write there that this is a pro feature and add a link to this page:

image

@github-actions
Copy link
Contributor

github-actions bot commented Nov 5, 2025

Documentation Link Check Results

Absolute links check failed
There are broken absolute links in the documentation. See workflow logs for details
Relative links check passed
Last checked: 2025-11-07 13:37:48 UTC

Copy link
Contributor

@htahir1 htahir1 left a comment

Choose a reason for hiding this comment

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

Requested some changes and left you some screenshots you can use

@htahir1
Copy link
Contributor

htahir1 commented Nov 5, 2025

Ah one more thing. Now that we have service accounts and personal access tokens might make sense to add a new section called "Access Management" in here (Same as Core Concepts, Deployments)

Screenshot 2025-11-05 135007 com/user-attachments/assets/f5b0bb08-5f07-44ab-9cab-6cd62c04ed48" />

@stefannica stefannica requested a review from htahir1 November 6, 2025 21:03
@github-actions
Copy link
Contributor

github-actions bot commented Nov 6, 2025

Images automagically compressed by Calibre's image-actions

Compression reduced images by 25.5%, saving 44.79 KB.

Filename Before After Improvement Visual comparison
docs/book/.gitbook/assets/pro-personal-access-tokens-01.png 175.50 KB 130.71 KB -25.5% View diff

380 images did not require optimisation.

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

@stefannica
Copy link
Contributor Author

stefannica commented Nov 6, 2025

@htahir1 I applied all your suggestions, please take a look here: https://zenml-io.gitbook.io/stefan/

Copy link
Contributor

@htahir1 htahir1 left a comment

Choose a reason for hiding this comment

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

This looks way better now - Just two things:

a) I think you are inferring the URLs wrongly. Best way is to map them to your preview so https://zenml-io.gitbook.io/stefan/zenml-pro/access-management/personal-access-tokens will be https://docs.zenml.io/pro/access-management/personal-access-tokens (Note that in your space its /zenml-pro/ but in the real space it will be /pro/)

b) You have not added redirects as I asked in the .gitbook.yaml ;-) Reminder :-)


# Connect with a Personal Access Token

If you are using ZenML Pro and need to call the ZenML Pro workspace API from a non-interactive environment, you also have the option of creating and using a Personal Access Token. Personal Access Tokens are scoped to your ZenML Pro user account and can be used to access all workspaces you are a member of in any organization. See the [ZenML Pro Personal Access Tokens](https://docs.zenml.io/pro/core-concepts/personal-access-tokens) documentation for more information.
Copy link
Contributor

Choose a reason for hiding this comment

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

```

If you're using a ZenML Pro server, you will need to create an organization-level service account and an API key for it. You can find more about organization-level service accounts and API keys [here](https://docs.zenml.io/pro/core-concepts/service-accounts).
If you're using a ZenML Pro server, you will need to create a Personal Access Token or an organization-level service account and an API key for it. You can find more about Personal Access Tokens [here](https://docs.zenml.io/pro/core-concepts/personal-access-tokens) and organization-level service accounts and API keys [here](https://docs.zenml.io/pro/core-concepts/service-accounts).
Copy link
Contributor

Choose a reason for hiding this comment

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



If you're using a ZenML Pro server, you will need to create an organization-level service account and an API key for it. You can find more about organization-level service accounts and API keys [here](https://docs.zenml.io/pro/core-concepts/service-accounts).
If you're using a ZenML Pro server, you will need to create a Personal Access Token or an organization-level service account and an API key for it. You can find more about Personal Access Tokens [here](https://docs.zenml.io/pro/core-concepts/personal-access-tokens) and organization-level service accounts and API keys [here](https://docs.zenml.io/pro/core-concepts/service-accounts).
Copy link
Contributor

Choose a reason for hiding this comment

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

@github-actions
Copy link
Contributor

github-actions bot commented Nov 7, 2025

ZenML CLI Performance Comparison (Threshold: 1.0s, Timeout: 60s, Slow: 5s)

❌ Failed Commands on Current Branch (feature/deprecate-api-tokens)

  • zenml stack list: Command failed on run 1 (exit code: 1)
  • zenml pipeline list: Command failed on run 1 (exit code: 1)
  • zenml model list: Command failed on run 1 (exit code: 1)

🚨 New Failures Introduced

The following commands fail on your branch but worked on the target branch:

  • zenml stack list
  • zenml pipeline list
  • zenml model list

Performance Comparison

Command develop Time (s) feature/deprecate-api-tokens Time (s) Difference Status
zenml --help 1.477796 ± 0.008124 1.464350 ± 0.017464 -0.013s ✓ No significant change
zenml model list Not tested Failed N/A ❌ Broken in current branch
zenml pipeline list Not tested Failed N/A ❌ Broken in current branch
zenml stack --help 1.467600 ± 0.023152 1.468313 ± 0.025495 ±0.000s ✓ No significant change
zenml stack list Not tested Failed N/A ❌ Broken in current branch

Summary

  • Total commands analyzed: 5
  • Commands compared for timing: 2
  • Commands improved: 0 (0.0% of compared)
  • Commands degraded: 0 (0.0% of compared)
  • Commands unchanged: 2 (100.0% of compared)
  • Failed commands: 3 (NEW FAILURES INTRODUCED)
  • Timed out commands: 0
  • Slow commands: 0

Environment Info

  • Target branch: Linux 6.11.0-1018-azure
  • Current branch: Linux 6.11.0-1018-azure
  • Test timestamp: 2025-11-07T13:32:22Z
  • Timeout: 60 seconds
  • Slow threshold: 5 seconds

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