Add pipeline deployment to onboarding (#4231)

* Add snapshot creation and deployment tracking to onboarding

This adds backend support for tracking two new onboarding steps related
to pipeline snapshots: snapshot creation and deployment. These steps help
guide users through the workflow of creating and deploying pipeline snapshots.

Changes:
- Add SNAPSHOT_CREATED and SNAPSHOT_DEPLOYED enum values to OnboardingStep
- Track SNAPSHOT_CREATED in create_snapshot method when users create a snapshot
- Track SNAPSHOT_DEPLOYED in create_deployment method when users deploy a snapshot

This implements backend support for zenml-io/zenml-dashboard#913

* Only track SNAPSHOT_CREATED for user-created named snapshots

Modified the SNAPSHOT_CREATED onboarding tracking to only fire for
user-created snapshots with names, not for internal system-generated
snapshots created during pipeline runs. This prevents false positives
in the onboarding flow.

When run_snapshot is called internally, it creates unnamed snapshots
that shouldn't count toward user onboarding progress.

* Update src/zenml/zen_stores/sql_zen_store.py

* Remove SNAPSHOT_CREATED tracking from onboarding

Based on product feedback, removed SNAPSHOT_CREATED enum and tracking
since snapshot creation and deployment happen in the same onboarding
step (collapsible section). Only SNAPSHOT_DEPLOYED tracking remains
to mark when users deploy their pipeline.

This aligns with the simplified onboarding flow where users will
directly deploy pipelines via `zenml pipeline deploy` command.

* Clean up merge conflict markers - remove SNAPSHOT_CREATED tracking

* Rename to PIPELINE_DEPLOYED and gate onboarding completion

Changes:
- Renamed SNAPSHOT_DEPLOYED to PIPELINE_DEPLOYED to align with new terminology
- Moved OSS_ONBOARDING_COMPLETED and PRO_ONBOARDING_COMPLETED to trigger
  only when PIPELINE_DEPLOYED event fires (when user deploys a pipeline)
- Removed automatic onboarding completion from pipeline run logic

This ensures users must complete the full onboarding flow including
deployment before onboarding is marked as complete.

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: htahir1

src/zenml/enums.py

@@ -507,6 +507,7 @@ class OnboardingStep(StrEnum):
     PIPELINE_RUN_WITH_REMOTE_ARTIFACT_STORE = (
         "pipeline_run_with_remote_artifact_store"
     )
+    PIPELINE_DEPLOYED = "pipeline_deployed"
     OSS_ONBOARDING_COMPLETED = "oss_onboarding_completed"
     PRO_ONBOARDING_COMPLETED = "pro_onboarding_completed"
 

src/zenml/zen_stores/sql_zen_store.py

@@ -5298,6 +5298,17 @@ def create_deployment(
             )
 
             session.refresh(deployment_schema)
+
+            # Track deployment and mark onboarding as completed
+            self._update_onboarding_state(
+                completed_steps={
+                    OnboardingStep.PIPELINE_DEPLOYED,
+                    OnboardingStep.OSS_ONBOARDING_COMPLETED,
+                    OnboardingStep.PRO_ONBOARDING_COMPLETED,
+                },
+                session=session,
+            )
+
             return deployment_schema.to_model(
                 include_metadata=True, include_resources=True
             )
@@ -10767,7 +10778,6 @@ def _update_pipeline_run_status(
 
             completed_onboarding_steps: Set[str] = {
                 OnboardingStep.PIPELINE_RUN,
-                OnboardingStep.OSS_ONBOARDING_COMPLETED,
             }
             if stack_metadata["orchestrator"] not in {
                 "local",
@@ -10782,7 +10792,6 @@ def _update_pipeline_run_status(
                 completed_onboarding_steps.update(
                     {
                         OnboardingStep.PIPELINE_RUN_WITH_REMOTE_ARTIFACT_STORE,
-                        OnboardingStep.PRO_ONBOARDING_COMPLETED,
                     }
                 )