From 5bf1852e3816e2c80989a78d117b285f77b63912 Mon Sep 17 00:00:00 2001
From: Robin Speekenbrink <robin@kingsquare.nl>
Date: Tue, 20 Aug 2024 11:48:15 +0200
Subject: [PATCH] Update .lagoon.yml

Use the optimize / optimize:clear handling instead of explicit

This also fixes the double view:cache calls (one was in the clear which was the wrong command)
---
 src/Commands/sailonLagoonAssets/.lagoon.yml | 9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/src/Commands/sailonLagoonAssets/.lagoon.yml b/src/Commands/sailonLagoonAssets/.lagoon.yml
index 2f47cb2..ac04972 100644
--- a/src/Commands/sailonLagoonAssets/.lagoon.yml
+++ b/src/Commands/sailonLagoonAssets/.lagoon.yml
@@ -17,17 +17,12 @@ tasks:
         shell: bash
     - run:
         name: Clear caches
-        command: php artisan -n cache:clear && php artisan -n route:clear && php artisan -n view:cache
+        command: php artisan -n optimize:clear
         service: cli
         shell: bash
     - run:
         name: Build caches when pushing to production
         when: LAGOON_ENVIRONMENT_TYPE == "production"
-        command: |
-          php artisan config:cache
-          php artisan route:cache
-          php artisan view:cache
-          php artisan event:cache
-          php artisan optimize
+        command: php artisan optimize
         service: cli
         shell: bash