-
Notifications
You must be signed in to change notification settings - Fork 442
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
Add option to add base URL for zenml server (with support for cloud) #2464
Conversation
Important Auto Review SkippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the To trigger a single review, invoke the 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? TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Additionally, you can add CodeRabbit Configration File (
|
Quickstart template updates in |
I think for the future we will also need the org id separately, I would not make it part of the base url. Base url should be: https://cloud.zenml.io/ I believe the tenant_id is already there |
…enml-io/zenml into feature/add-server-url-to-info
@AlexejPenner I made the base url, org and tenant ID available as separate variables. These variables are set in the environment through the terraform script in this PR: https://github.com/zenml-io/zenml-cloud-infra/pull/16 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good now, but if you want to go the extra mile and model the cloud_organization_id
setting as a generic metadata
dictionary instead, it would be even better.
…enml-io/zenml into feature/add-server-url-to-info
…enml-io#2464) * add base url as helm input and create env var * add server url as part of zenml info endpoint * Auto-update of Starter template * make org and tenant id available separately * add base url and org id to server config * add base url and org id to server model in base zen store * add base URL to helm template for env vars * make cloud org ID opauqe and part of server metadata * make metadata a Dict type object * if metadata is str, convert to dict * fix linter issue * make empty dict as default metadata value * Add server metadata to analytics --------- Co-authored-by: GitHub Actions <[email protected]> Co-authored-by: Michael Schuster <[email protected]>
Describe changes
I implemented changes to allow
This is exposed through the
/info
endpoint of the server. The use case is to allow ZenML to use the URL to construct addresses for stuff like pipeline runs and other info on the server.Pre-requisites
Please ensure you have done the following:
develop
and the open PR is targetingdevelop
. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.Types of changes