zenml-nightly 0.58.0.dev20240529__tar.gz → 0.58.1.dev20240610__tar.gz

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/CONTRIBUTING.md

@@ -250,7 +250,7 @@ for detailed step-by-step instructions.
 [Examples README](examples/README.md) 
 to find out what to do.
 3. All integrations deserve to be documented. Make sure to pay a visit to the
-[Component Guide](https://docs.zenml.io/stacks-and-components/component-guide)
+[Component Guide](https://docs.zenml.io/stack-components/component-guide)
 in the docs and add your implementations. 
 
 ## 🆘 Getting Help

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: zenml-nightly
-Version: 0.58.0.dev20240529
+Version: 0.58.1.dev20240610
 Summary: ZenML: Write production-ready ML code.
 Home-page: https://zenml.io
 License: Apache-2.0
@@ -348,7 +348,7 @@ you can make use of a control plane to create ZenML servers, also known as tenan
 These tenants are managed and maintained by ZenML’s dedicated team, alleviating
 the burden of server management from your end.
 - **Self-hosted deployment**: Alternatively, you have the flexibility to [deploy
-ZenML on your own self-hosted environment](https://docs.zenml.io/deploying-zenml/zenml-self-hosted).
+ZenML on your own self-hosted environment](https://docs.zenml.io/getting-started/deploying-zenml#deploying-a-zenml-server).
 This can be achieved through various methods, including using our CLI, Docker,
 Helm, or HuggingFace Spaces.
 
@@ -426,10 +426,11 @@ the Apache License Version 2.0.
     <a href="https://github.com/zenml-io/zenml-projects">Projects Showcase</a>
     <br />
     <br />
-    🎉 Version 0.58.0 is out. Check out the release notes
+    🎉 Version 0.58.1 is out. Check out the release notes
     <a href="https://github.com/zenml-io/zenml/releases">here</a>.
     <br />
     🖥️ Download our VS Code Extension <a href="https://marketplace.visualstudio.com/items?itemName=ZenML.zenml-vscode">here</a>.
     <br />
   </p>
 </div>
+

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/README.md

@@ -211,7 +211,7 @@ you can make use of a control plane to create ZenML servers, also known as tenan
 These tenants are managed and maintained by ZenML’s dedicated team, alleviating
 the burden of server management from your end.
 - **Self-hosted deployment**: Alternatively, you have the flexibility to [deploy
-ZenML on your own self-hosted environment](https://docs.zenml.io/deploying-zenml/zenml-self-hosted).
+ZenML on your own self-hosted environment](https://docs.zenml.io/getting-started/deploying-zenml#deploying-a-zenml-server).
 This can be achieved through various methods, including using our CLI, Docker,
 Helm, or HuggingFace Spaces.
 
@@ -289,10 +289,10 @@ the Apache License Version 2.0.
     <a href="https://github.com/zenml-io/zenml-projects">Projects Showcase</a>
     <br />
     <br />
-    🎉 Version 0.58.0 is out. Check out the release notes
+    🎉 Version 0.58.1 is out. Check out the release notes
     <a href="https://github.com/zenml-io/zenml/releases">here</a>.
     <br />
     🖥️ Download our VS Code Extension <a href="https://marketplace.visualstudio.com/items?itemName=ZenML.zenml-vscode">here</a>.
     <br />
   </p>
-</div>
+</div>

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/RELEASE_NOTES.md

@@ -1,5 +1,41 @@
 <!-- markdown-link-check-disable -->
 
+# 0.58.1
+
+The 0.58.1 release brings a set of minor enhancement and bugfix to the ZenML framework, such as the ability to delete all versions of a pipeline using the Client/CLI, providing greater flexibility and control over pipeline management. Users can now specify Python package installer arguments. Furthermore, a fix has been implemented for the Sentencepiece tokenizer materializer.
+
+We are also excited to announce the introduction of breadcrumbs to our dashboard to improve your navigation experience. This new feature allows you to easily visualize the path of your Pipelines, Models, and Artifacts, providing clear orientation, quick return to any section with a single click, and effortless navigation.
+
+We’d like to give a special thanks to @eltociear for their first contribution.
+
+## Docs re-work
+
+We reworked the structure of our documentation pages to make it easier to find answers to your practical questions. Please do let us know if you have any feedback on the structure or the new style of the 'How To' section!
+
+## What's Changed
+* Add 0.58.0 to migration testing by @avishniakov in https://github.com/zenml-io/zenml/pull/2730
+* Print step names in color, again by @avishniakov in https://github.com/zenml-io/zenml/pull/2728
+* Workflow to create JIRA tickets when Github Issues are created by @strickvl in https://github.com/zenml-io/zenml/pull/2724
+* Allow specifying python package installer args by @schustmi in https://github.com/zenml-io/zenml/pull/2727
+* Send workflow dispatch event to Cloud Plugins repo on release by @wjayesh in https://github.com/zenml-io/zenml/pull/2633
+* Fix Nightly Release by @safoinme in https://github.com/zenml-io/zenml/pull/2711
+* Fix `zenml go` images visibility in notebook by @strickvl in https://github.com/zenml-io/zenml/pull/2742
+* Handle error when using `zenml info` with missing dependencies by @strickvl in https://github.com/zenml-io/zenml/pull/2725
+* Add Discord Alerter into TOC by @strickvl in https://github.com/zenml-io/zenml/pull/2735
+* Allow deleting all versions of a pipeline using the Client/CLI by @schustmi in https://github.com/zenml-io/zenml/pull/2745
+* Misc fixes by @schustmi in https://github.com/zenml-io/zenml/pull/2732
+* Move full SQLite DB migration test to slow CI by @strickvl in https://github.com/zenml-io/zenml/pull/2743
+* Add system flag as default for uv by @schustmi in https://github.com/zenml-io/zenml/pull/2748
+* Add how-to section & restructure/update documentation by @AlexejPenner in https://github.com/zenml-io/zenml/pull/2705
+* Fix typo in help text by @eltociear in https://github.com/zenml-io/zenml/pull/2750
+* Add support for function types in source utils by @schustmi in https://github.com/zenml-io/zenml/pull/2738
+* Fix Sentencepiece tokenizer materializer by @safoinme in https://github.com/zenml-io/zenml/pull/2751
+
+## New Contributors
+* @eltociear made their first contribution in https://github.com/zenml-io/zenml/pull/2750
+
+**Full Changelog**: https://github.com/zenml-io/zenml/compare/0.58.0...0.58.1
+
 # 0.58.0
 
 ## New Annotators
@@ -1820,7 +1856,7 @@ This is a minor ZenML release that introduces a couple of new features:
 
 In addition to that, this release also contains a couple of bug fixes and improvements, including:
 
-* better documentation and fixes for the ZenML [Vertex AI Orchestrator](https://docs.zenml.io/stacks-and-components/component-guide/orchestrators/vertex) and [Vertex AI Step Operator](https://docs.zenml.io/stacks-and-components/component-guide/step-operators/vertex)
+* better documentation and fixes for the ZenML [Vertex AI Orchestrator](https://docs.zenml.io/stack-components/orchestrators/vertex) and [Vertex AI Step Operator](https://docs.zenml.io/stack-components/step-operators/vertex)
 * adjust Seldon and BentoML Steps and Examples to new pipeline interface
 
 ## What's Changed

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "zenml-nightly"
-version = "0.58.0.dev20240529"
+version = "0.58.1.dev20240610"
 packages = [{ include = "zenml", from = "src" }]
 description = "ZenML: Write production-ready ML code."
 authors = ["ZenML GmbH <info@zenml.io>"]

zenml_nightly-0.58.1.dev20240610/src/zenml/VERSION

@@ -0,0 +1 @@
+0.58.1.dev20240610

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/src/zenml/artifacts/utils.py

@@ -684,7 +684,7 @@ def _load_artifact_store(
             StackComponent.from_model(artifact_store_model),
         )
     except ImportError:
-        link = "https://docs.zenml.io/stacks-and-components/component-guide/artifact-stores/custom#enabling-artifact-visualizations-with-custom-artifact-stores"
+        link = "https://docs.zenml.io/stack-components/artifact-stores/custom#enabling-artifact-visualizations-with-custom-artifact-stores"
         raise NotImplementedError(
             f"Artifact store '{artifact_store_model.name}' could not be "
             f"instantiated. This is likely because the artifact store's "
@@ -745,6 +745,8 @@ def _load_file_from_artifact_store(
     uri: str,
     artifact_store: "BaseArtifactStore",
     mode: str = "rb",
+    offset: int = 0,
+    length: Optional[int] = None,
 ) -> Any:
     """Load the given uri from the given artifact store.
 
@@ -752,6 +754,8 @@ def _load_file_from_artifact_store(
         uri: The uri of the file to load.
         artifact_store: The artifact store from which to load the file.
         mode: The mode in which to open the file.
+        offset: The offset from which to start reading.
+        length: The amount of bytes that should be read.
 
     Returns:
         The loaded file.
@@ -763,7 +767,19 @@ def _load_file_from_artifact_store(
     """
     try:
         with artifact_store.open(uri, mode) as text_file:
-            return text_file.read()
+            if offset < 0:
+                # If the offset is negative, we seek backwards from the end of
+                # the file
+                try:
+                    text_file.seek(offset, os.SEEK_END)
+                except OSError:
+                    # The negative offset was too large for the file, we seek
+                    # to the start of the file
+                    text_file.seek(0, os.SEEK_SET)
+            elif offset > 0:
+                text_file.seek(offset, os.SEEK_SET)
+
+            return text_file.read(length)
     except FileNotFoundError:
         raise DoesNotExistException(
             f"File '{uri}' does not exist in artifact store "
@@ -773,7 +789,7 @@ def _load_file_from_artifact_store(
         raise e
     except Exception as e:
         logger.exception(e)
-        link = "https://docs.zenml.io/stacks-and-components/component-guide/artifact-stores/custom#enabling-artifact-visualizations-with-custom-artifact-stores"
+        link = "https://docs.zenml.io/stack-components/artifact-stores/custom#enabling-artifact-visualizations-with-custom-artifact-stores"
         raise NotImplementedError(
             f"File '{uri}' could not be loaded because the underlying artifact "
             f"store '{artifact_store.name}' could not open the file. This is "

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/src/zenml/cli/__init__.py

@@ -80,7 +80,7 @@ You can also pass in a directory path manually using the
 zenml init --path /path/to/dir
 ```
 
-If you wish to use one of [the available ZenML project templates](https://docs.zenml.io/user-guide/starter-guide/using-project-templates#list-of-zenml-project-templates)
+If you wish to use one of [the available ZenML project templates](https://docs.zenml.io/how-to/setting-up-a-project-repository/using-project-templates#list-of-zenml-project-templates)
 to generate a ready-to-use project scaffold in your repository, you can do so by
 passing the ``--template`` option:
 
@@ -232,7 +232,7 @@ and `and` keywords.
 Artifact Stores
 ---------------
 
-In ZenML, [the artifact store](https://docs.zenml.io/stacks-and-components/component-guide/artifact-stores)
+In ZenML, [the artifact store](https://docs.zenml.io/stack-components/artifact-stores)
 is where all the inputs and outputs of your pipeline steps are stored. By
 default, ZenML initializes your repository with an artifact store with
 everything kept on your local machine. You can get a better understanding
@@ -327,7 +327,7 @@ zenml artifact-store --help
 Orchestrators
 -------------
 
-An [orchestrator](https://docs.zenml.io/stacks-and-components/component-guide/orchestrators)
+An [orchestrator](https://docs.zenml.io/stack-components/orchestrators)
 is a special kind of backend that manages the running of each step of the
 pipeline. Orchestrators administer the actual pipeline runs. By default,
 ZenML initializes your repository with an orchestrator that runs everything
@@ -423,7 +423,7 @@ zenml orchestrators --help
 Container Registries
 --------------------
 
-[The container registry](https://docs.zenml.io/stacks-and-components/component-guide/container-registries)
+[The container registry](https://docs.zenml.io/stack-components/container-registries)
 is where all the images that are used by a container-based orchestrator are
 stored. To get a better understanding regarding container registries, use
 the command:
@@ -518,7 +518,7 @@ zenml container-registry --help
 Data Validators
 ---------------
 
-In ZenML, [data validators](https://docs.zenml.io/stacks-and-components/component-guide/data-validators)
+In ZenML, [data validators](https://docs.zenml.io/stack-components/data-validators)
 help you profile and validate your data.
 
 By default, a default ZenML local stack will not register a data validator. If
@@ -605,7 +605,7 @@ zenml data-validator --help
 Experiment Trackers
 -------------------
 
-[Experiment trackers](https://docs.zenml.io/stacks-and-components/component-guide/experiment-trackers)
+[Experiment trackers](https://docs.zenml.io/stack-components/experiment-trackers)
  let you track your ML experiments by logging the parameters
 and allow you to compare between different runs. To get a better
 understanding regarding experiment trackers, use the command:
@@ -701,7 +701,7 @@ zenml experiment-tracker --help
 Model Deployers
 ---------------
 
-[Model deployers](https://docs.zenml.io/stacks-and-components/component-guide/model-deployers)
+[Model deployers](https://docs.zenml.io/stack-components/model-deployers)
 are stack components responsible for online model serving. They are responsible
 for deploying models to a remote server. Model deployers also act as a registry
 for models that are served with ZenML. To get a better understanding regarding
@@ -838,7 +838,7 @@ zenml model-deployer --help
 Step Operators
 --------------
 
-[Step operators](https://docs.zenml.io/stacks-and-components/component-guide/step-operators)
+[Step operators](https://docs.zenml.io/stack-components/step-operators)
 allow you to run individual steps in a custom environment different from the
 default one used by your active orchestrator. One example use-case is to run a
 training step of your pipeline in an environment with GPUs available. To get
@@ -933,7 +933,7 @@ zenml step-operator --help
 Alerters
 --------
 
-In ZenML, [alerters](https://docs.zenml.io/stacks-and-components/component-guide/alerters)
+In ZenML, [alerters](https://docs.zenml.io/stack-components/alerters)
 allow you to send alerts from within your pipeline.
 
 By default, a default ZenML local stack will not register an alerter. If
@@ -1018,7 +1018,7 @@ zenml alerter --help
 Feature Stores
 --------------
 
-[Feature stores](https://docs.zenml.io/stacks-and-components/component-guide/feature-stores)
+[Feature stores](https://docs.zenml.io/stack-components/feature-stores)
 allow data teams to serve data via an offline store and an online low-latency
 store where data is kept in sync between the two. To get a better understanding
 regarding feature stores, use the command:
@@ -1115,7 +1115,7 @@ zenml feature-store --help
 Annotators
 ----------
 
-[Annotators](https://docs.zenml.io/stacks-and-components/component-guide/annotators)
+[Annotators](https://docs.zenml.io/stack-components/annotators)
 enable the use of data annotation as part of your ZenML stack and pipelines.
 
 By default, a default ZenML local stack will not register an annotator. If
@@ -1207,7 +1207,7 @@ zenml annotator --help
 Image Builders
 --------------
 
-In ZenML, [image builders](https://docs.zenml.io/stacks-and-components/component-guide/image-builders)
+In ZenML, [image builders](https://docs.zenml.io/stack-components/image-builders)
 allow you to build container images such
 that your machine-learning pipelines and steps can be executed in remote
 environments.
@@ -1296,7 +1296,7 @@ zenml image-builder --help
 Model Registries
 ----------------
 
-[Model registries](https://docs.zenml.io/stacks-and-components/component-guide/model-registries)
+[Model registries](https://docs.zenml.io/stack-components/model-registries)
 are centralized repositories that facilitate the collaboration and management
 of machine learning models. To get a better understanding regarding model
 registries as a concept, use the command:
@@ -1672,8 +1672,14 @@ occasionally want to delete a pipeline, which you can do via:
 zenml pipeline delete <PIPELINE_NAME>
 ```
 
-This will delete the pipeline and change all corresponding pipeline runs to
-become unlisted (not linked to any pipeline).
+This will delete the latest pipeline version and change all corresponding
+pipeline runs to become unlisted (not linked to any pipeline).
+
+If you want to delete all versions of a pipeline, you can do so as follows:
+
+```bash
+zenml pipeline delete <PIPELINE_NAME> --all-versions
+```
 
 To list all pipeline runs that you have executed, use:
 
@@ -1828,7 +1834,7 @@ Connecting to a ZenML Server
 ----------------------------
 
 The ZenML client can be [configured to connect to a remote database or ZenML
-server](https://docs.zenml.io/user-guide/advanced-guide/configuring-zenml/connecting-to-zenml)
+server](https://docs.zenml.io/how-to/connecting-to-zenml)
 with the `zenml connect` command. If no arguments are supplied, ZenML
 will attempt to connect to the last ZenML server deployed from the local host
 using the 'zenml deploy' command:
@@ -1980,7 +1986,7 @@ Secrets management
 ------------------
 
 ZenML offers a way to [securely store secrets associated with your other
-stack components and infrastructure](https://docs.zenml.io/user-guide/advanced-guide/secret-management).
+stack components and infrastructure](https://docs.zenml.io/getting-started/deploying-zenml/manage-the-deployed-services/secret-management).
 A ZenML Secret is a collection or grouping of key-value pairs stored by the
 ZenML secrets store. ZenML Secrets are identified by a unique name which
 allows you to fetch or reference them in your pipelines and stacks.
@@ -2076,7 +2082,7 @@ challenge in configuring uninterrupted, secure access to infrastructure
 resources. In ZenML, Service Connectors streamline this process by abstracting
 away the complexity of authentication and help you connect your stack to your
 resources. You can find the full docs on the ZenML service connectors
-[here](https://docs.zenml.io/stacks-and-components/auth-management).
+[here](https://docs.zenml.io/how-to/auth-management).
 
 The ZenML CLI features a variety of commands to help you manage your service
 connectors. First of all, to explore all the types of service connectors
@@ -2106,7 +2112,7 @@ zenml service-connector register SERVICE_CONNECTOR_NAME \
 ```
 
 For more details on how to create a service connector, please refer to our
-[docs](https://docs.zenml.io/stacks-and-components/auth-management).
+[docs](https://docs.zenml.io/how-to/auth-management).
 
 To check if your service connector is registered properly, you can `verify` it.
 By doing this, you can both check if it is configured correctly and also, you
@@ -2338,7 +2344,7 @@ zenml code-repository delete <REPOSITORY_NAME_OR_ID>
 Building an image without Runs
 ------------------------------
 
-To [build Docker images for your pipeline](https://docs.zenml.io/user-guide/advanced-guide/infrastructure-management/containerize-your-pipeline)
+To [build Docker images for your pipeline](https://docs.zenml.io/how-to/customize-docker-builds)
 without actually running the pipeline, use:
 
 ```bash
@@ -2385,7 +2391,7 @@ Tagging your resources with ZenML
 ---------------------------------
 
 When you are using ZenML, you can [use tags to organize and categorize your
-assets](https://docs.zenml.io/user-guide/advanced-guide/data-management/tagging).
+assets](https://docs.zenml.io/how-to/handle-data-artifacts/tagging).
 This way, you can streamline your workflows and enhance the discoverability of
 your resources more easily.
 
@@ -2487,7 +2493,7 @@ zenml artifact-store deploy -f gcp -p gcp -r us-east1 -x project_id=zenml-core b
 ```
 
 For full documentation on this functionality, please refer to [the dedicated
-documentation on stack component deploy](https://docs.zenml.io/stacks-and-components/stack-deployment/deploy-a-stack-component).
+documentation on stack component deploy](https://docs.zenml.io/how-to/stack-deployment/deploy-a-stack-component).
 
 Interacting with the ZenML Hub
 ------------------------------

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/src/zenml/cli/base.py

@@ -79,19 +79,19 @@ class ZenMLProjectTemplateLocation(BaseModel):
 ZENML_PROJECT_TEMPLATES = dict(
     e2e_batch=ZenMLProjectTemplateLocation(
         github_url="zenml-io/template-e2e-batch",
-        github_tag="2024.04.05",  # Make sure it is aligned with .github/workflows/update-templates-to-examples.yml
+        github_tag="2024.06.06",  # Make sure it is aligned with .github/workflows/update-templates-to-examples.yml
     ),
     starter=ZenMLProjectTemplateLocation(
         github_url="zenml-io/template-starter",
-        github_tag="2024.04.03",  # Make sure it is aligned with .github/workflows/update-templates-to-examples.yml
+        github_tag="2024.06.06",  # Make sure it is aligned with .github/workflows/update-templates-to-examples.yml
     ),
     nlp=ZenMLProjectTemplateLocation(
         github_url="zenml-io/template-nlp",
-        github_tag="2024.04.05",  # Make sure it is aligned with .github/workflows/update-templates-to-examples.yml
+        github_tag="2024.06.06",  # Make sure it is aligned with .github/workflows/update-templates-to-examples.yml
     ),
     llm_finetuning=ZenMLProjectTemplateLocation(
         github_url="zenml-io/template-llm-finetuning",
-        github_tag="2024.05.23",  # Make sure it is aligned with .github/workflows/update-templates-to-examples.yml
+        github_tag="2024.06.06",  # Make sure it is aligned with .github/workflows/update-templates-to-examples.yml
     ),
 )
 
@@ -492,7 +492,10 @@ def go() -> None:
         input("Press ENTER to continue...")
 
     try:
-        subprocess.check_call(["jupyter", "notebook"], cwd=zenml_tutorial_path)
+        subprocess.check_call(
+            ["jupyter", "notebook", "--ContentsManager.allow_hidden=True"],
+            cwd=zenml_tutorial_path,
+        )
     except subprocess.CalledProcessError as e:
         cli_utils.error(
             "An error occurred while launching Jupyter Notebook. "
@@ -653,7 +656,15 @@ def info(
         cli_utils.print_user_info(user_info)
 
     if stack:
-        cli_utils.print_debug_stack()
+        try:
+            cli_utils.print_debug_stack()
+        except ModuleNotFoundError as e:
+            cli_utils.warning(
+                "Could not print debug stack information. Please make sure "
+                "you have the necessary dependencies and integrations "
+                "installed for all your stack components."
+            )
+            cli_utils.warning(f"The missing package is: '{e.name}'")
 
 
 @cli.command(

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/src/zenml/cli/pipeline.py

@@ -327,6 +327,11 @@ def list_pipelines(**kwargs: Any) -> None:
     type=str,
     required=False,
 )
+@click.option(
+    "--all-versions",
+    help="Delete all versions of the pipeline..",
+    is_flag=True,
+)
 @click.option(
     "--yes",
     "-y",
@@ -334,16 +339,24 @@ def list_pipelines(**kwargs: Any) -> None:
     help="Don't ask for confirmation.",
 )
 def delete_pipeline(
-    pipeline_name_or_id: str, version: Optional[str] = None, yes: bool = False
+    pipeline_name_or_id: str,
+    version: Optional[str] = None,
+    all_versions: bool = False,
+    yes: bool = False,
 ) -> None:
     """Delete a pipeline.
 
     Args:
         pipeline_name_or_id: The name or ID of the pipeline to delete.
         version: The version of the pipeline to delete.
+        all_versions: If set, delete all versions of the pipeline.
         yes: If set, don't ask for confirmation.
     """
-    version_suffix = f" (version {version})" if version else ""
+    version_suffix = ""
+    if all_versions:
+        version_suffix = " (all versions)"
+    elif version:
+        version_suffix = f" (version {version})"
 
     if not yes:
         confirmation = cli_utils.confirmation(
@@ -357,7 +370,9 @@ def delete_pipeline(
 
     try:
         Client().delete_pipeline(
-            name_id_or_prefix=pipeline_name_or_id, version=version
+            name_id_or_prefix=pipeline_name_or_id,
+            version=version,
+            all_versions=all_versions,
         )
     except KeyError as e:
         cli_utils.error(str(e))

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/src/zenml/cli/server.py

@@ -737,7 +737,7 @@ def connect(
             "filesystem. You should consider using the web login workflow by "
             "omitting the `--username` and `--password` flags. An alternative "
             "for non-interactive environments is to create and use a service "
-            "account API key (see https://docs.zenml.io/user-guide/advanced-guide/configuring-zenml/connecting-to-zenml#using-service-accounts-to-connect-to-a-deployed-zenml-server "
+            "account API key (see https://docs.zenml.io/how-to/connecting-to-zenml/connect-with-a-service-account "
             "for more information)."
         )
 

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/src/zenml/cli/stack.py

@@ -489,7 +489,7 @@ def update_stack(
     "-r",
     "--model_registry",
     "model_registry_flag",
-    help="Include this to remove the the model registry from this stack.",
+    help="Include this to remove the model registry from this stack.",
     is_flag=True,
     required=False,
 )

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/src/zenml/client.py

@@ -2415,6 +2415,7 @@ class Client(metaclass=ClientMetaClass):
         self,
         name_id_or_prefix: Union[str, UUID],
         version: Optional[str] = None,
+        all_versions: bool = False,
     ) -> None:
         """Delete a pipeline.
 
@@ -2422,11 +2423,30 @@ class Client(metaclass=ClientMetaClass):
             name_id_or_prefix: The name, ID or ID prefix of the pipeline.
             version: The pipeline version. If left empty, will delete
                 the latest version.
+            all_versions: If `True`, delete all versions of the pipeline.
+
+        Raises:
+            ValueError: If an ID is supplied when trying to delete all versions
+                of a pipeline.
         """
-        pipeline = self.get_pipeline(
-            name_id_or_prefix=name_id_or_prefix, version=version
-        )
-        self.zen_store.delete_pipeline(pipeline_id=pipeline.id)
+        if all_versions:
+            if is_valid_uuid(name_id_or_prefix):
+                raise ValueError(
+                    "You need to supply a name (not an ID) when trying to "
+                    "delete all versions of a pipeline."
+                )
+
+            for pipeline in depaginate(
+                functools.partial(
+                    Client().list_pipelines, name=name_id_or_prefix
+                )
+            ):
+                Client().delete_pipeline(pipeline.id)
+        else:
+            pipeline = self.get_pipeline(
+                name_id_or_prefix=name_id_or_prefix, version=version
+            )
+            self.zen_store.delete_pipeline(pipeline_id=pipeline.id)
 
     # -------------------------------- Builds ----------------------------------
 

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/src/zenml/config/docker_settings.py

@@ -128,6 +128,8 @@ class DockerSettings(BaseSettings):
             therefore **not** include any registry.
         python_package_installer: The package installer to use for python
             packages.
+        python_package_installer_args: Arguments to pass to the python package
+            installer.
         replicate_local_python_environment: If not `None`, ZenML will use the
             specified method to generate a requirements file that replicates
             the packages installed in the currently running python environment.
@@ -185,6 +187,7 @@ class DockerSettings(BaseSettings):
     python_package_installer: PythonPackageInstaller = (
         PythonPackageInstaller.PIP
     )
+    python_package_installer_args: Dict[str, Any] = {}
     replicate_local_python_environment: Optional[
         Union[List[str], PythonEnvironmentExportMethod]
     ] = None

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/src/zenml/config/global_config.py

@@ -260,7 +260,7 @@ class GlobalConfiguration(BaseModel, metaclass=GlobalConfigMetaClass):
                     "The ZenML global configuration version (%s) is higher "
                     "than the version of ZenML currently being used (%s). "
                     "Read more about this issue and how to solve it here: "
-                    "`https://docs.zenml.io/user-guide/advanced-guide/environment-management/global-settings-of-zenml#version-mismatch-downgrading`",
+                    "`https://docs.zenml.io/reference/global-settings#version-mismatch-downgrading`",
                     config_version,
                     curr_version,
                 )

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/src/zenml/config/secret_reference_mixin.py

@@ -65,7 +65,7 @@ class SecretReferenceMixin(BaseModel):
                         "but future versions of ZenML will require you to pass "
                         "in sensitive information as secrets. Check out the "
                         "documentation on how to configure values with secrets "
-                        "here: https://docs.zenml.io/user-guide/advanced-guide/secret-management"
+                        "here: https://docs.zenml.io/getting-started/deploying-zenml/manage-the-deployed-services/secret-management"
                     )
                 continue
 

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/src/zenml/environment.py

@@ -439,7 +439,7 @@ class Environment(metaclass=SingletonMetaClass):
                 "will be removed in a future release. Please use the "
                 " `StepContext` to access information about the current run "
                 "instead, as shown here: "
-                "https://docs.zenml.io/user-guide/advanced-guide/pipelining-features/fetch-metadata-within-steps"
+                "https://docs.zenml.io/how-to/track-metrics-metadata/fetch-metadata-within-steps"
             )
         if name in self._components:
             return self._components[name]

{zenml_nightly-0.58.0.dev20240529 → zenml_nightly-0.58.1.dev20240610}/src/zenml/integrations/huggingface/materializers/huggingface_tokenizer_materializer.py

@@ -46,12 +46,11 @@ class HFTokenizerMaterializer(BaseMaterializer):
         Returns:
             The tokenizer read from the specified dir.
         """
-        temp_dir = TemporaryDirectory()
-        io_utils.copy_dir(
-            os.path.join(self.uri, DEFAULT_TOKENIZER_DIR), temp_dir.name
-        )
-
-        return AutoTokenizer.from_pretrained(temp_dir.name)
+        with TemporaryDirectory() as temp_dir:
+            io_utils.copy_dir(
+                os.path.join(self.uri, DEFAULT_TOKENIZER_DIR), temp_dir
+            )
+            return AutoTokenizer.from_pretrained(temp_dir)
 
     def save(self, tokenizer: Type[Any]) -> None:
         """Writes a Tokenizer to the specified dir.
@@ -59,9 +58,9 @@ class HFTokenizerMaterializer(BaseMaterializer):
         Args:
             tokenizer: The HFTokenizer to write.
         """
-        temp_dir = TemporaryDirectory()
-        tokenizer.save_pretrained(temp_dir.name)
-        io_utils.copy_dir(
-            temp_dir.name,
-            os.path.join(self.uri, DEFAULT_TOKENIZER_DIR),
-        )
+        with TemporaryDirectory() as temp_dir:
+            tokenizer.save_pretrained(temp_dir)
+            io_utils.copy_dir(
+                temp_dir,
+                os.path.join(self.uri, DEFAULT_TOKENIZER_DIR),
+            )