Fixed wandb login problem in Quickstart (#3233)

* Added wandb env variable

* Disable WANDB in training configurations for AWS, Azure, GCP.- Set WANDB_DISABLED to true in environment variables

examples/quickstart/configs/training_aws.yaml

@@ -4,6 +4,9 @@ settings:
     parent_image: "715803424590.dkr.ecr.eu-central-1.amazonaws.com/zenml-public-pipelines:quickstart-0.70.0-py3.11-aws"
     skip_build: True  # If you switch this to False remove the parent_image
     requirements: requirements.txt
+    environment:
+      WANDB_DISABLED: "true"
+
   orchestrator.sagemaker:
     instance_type: ml.m5.4xlarge
 

examples/quickstart/configs/training_azure.yaml

@@ -4,6 +4,8 @@ settings:
     parent_image: "zenmldocker/zenml-public-pipelines:quickstart-0.70.0-py3.11-azure"
     skip_build: True
     requirements: requirements.txt
+    environment:
+      WANDB_DISABLED: "true"
   # Uncomment the following lines to specify the accelerator for your azureml orchestrator
 #  orchestrator.azureml:
 #    mode: "compute-instance"

examples/quickstart/configs/training_default.yaml

@@ -2,6 +2,8 @@
 settings:
   docker:
     requirements: requirements.txt
+    environment:
+      WANDB_DISABLED: "true"
 
 # Model Control Plane configuration
 model:

examples/quickstart/configs/training_gcp.yaml

@@ -4,6 +4,8 @@ settings:
     parent_image: "zenmldocker/zenml-public-pipelines:quickstart-0.70.0-py3.11-gcp"
     skip_build: True
     requirements: requirements.txt
+    environment:
+      WANDB_DISABLED: "true"
 # Uncomment the following two lines to specify the accelerator for your vertex orchestrator
 #  orchestrator.vertex:
 #    node_selector_constraint: ["cloud.google.com/gke-accelerator", "NVIDIA_TESLA_P4"]