fix sorbet safe mode

Author: SylvainSenechal

solution/deps.yaml

@@ -109,11 +109,11 @@ scuba:
   tag: 1.1.0-preview.9
   envsubst: SCUBA_TAG
 sorbet:
-  sourceRegistry: ghcr.io/scality
+  sourceRegistry: ghcr.io/scality/playground/sylvainsenechal
   policy: sorbet/sorbet-policies
   dashboard: sorbet/sorbet-dashboards
   image: sorbet
-  tag: v1.2.2
+  tag: v100.1.0
   envsubst: SORBET_TAG
 stern: # tail any pod logs with pattern matchin
   tag: 1.33.0

tests/ctst/features/azureArchive.feature

@@ -1,32 +1,5 @@
 Feature: Azure Archive
 
-    @2.7.0
-    @PreMerge
-    @Flaky
-    @AzureArchive
-    @ColdStorage
-    Scenario Outline: Failed restore objects from tar must be retried and restored
-    Given a "<versioningConfiguration>" bucket
-    And a transition workflow to "e2e-azure-archive" location
-    And <objectCount> objects "retry-obj" of size <objectSize> bytes
-    Then object "retry-obj-1" should be "transitioning" and have the storage class "e2e-azure-archive"
-    And object "retry-obj-2" should be "transitioning" and have the storage class "e2e-azure-archive"
-    And manifest containing object "retry-obj-1" should "contain" object "retry-obj-2"
-    When i restore object "retry-obj-1" for <restoreDays> days
-    Then blob for object "retry-obj-1" fails to rehydrate
-    And blob for object "retry-obj-2" fails to rehydrate
-    Then object "retry-obj-1" should be "transitioning" and have the storage class "e2e-azure-archive"
-    When i run sorbetctl to retry failed restore for "e2e-azure-archive" location
-    Then object "retry-obj-1" should be "restored" and have the storage class "e2e-azure-archive"
-    And object "retry-obj-1" should expire in <restoreDays> days
-    And object "retry-obj-1" should have the same data
-
-    Examples:
-        | versioningConfiguration | objectCount | objectSize | restoreDays |
-        |           Non versioned |           2 |        100 |           5 |
-        |               Versioned |           2 |        100 |           2 |
-        |               Suspended |           2 |        100 |           2 | 
-
     @2.7.0
     @PreMerge
     @Flaky
@@ -251,6 +224,34 @@ Feature: Azure Archive
         |               Versioned |           2 |        100 |           15 |
         |               Suspended |           2 |        100 |           15 |
 
+
+    @2.7.0
+    @PreMerge
+    @Flaky
+    @AzureArchive
+    @ColdStorage
+    Scenario Outline: Failed restore objects from tar must be retried and restored
+    Given a "<versioningConfiguration>" bucket
+    And a transition workflow to "e2e-azure-archive" location
+    And <objectCount> objects "retry-obj" of size <objectSize> bytes
+    Then object "retry-obj-1" should be "transitioning" and have the storage class "e2e-azure-archive"
+    And object "retry-obj-2" should be "transitioning" and have the storage class "e2e-azure-archive"
+    And manifest containing object "retry-obj-1" should "contain" object "retry-obj-2"
+    When i restore object "retry-obj-1" for <restoreDays> days
+    Then blob for object "retry-obj-1" fails to rehydrate
+    And blob for object "retry-obj-2" fails to rehydrate
+    Then object "retry-obj-1" should be "transitioning" and have the storage class "e2e-azure-archive"
+    When i run sorbetctl to retry failed restore for "e2e-azure-archive" location
+    Then object "retry-obj-1" should be "restored" and have the storage class "e2e-azure-archive"
+    And object "retry-obj-1" should expire in <restoreDays> days
+    And object "retry-obj-1" should have the same data
+
+    Examples:
+        | versioningConfiguration | objectCount | objectSize | restoreDays |
+        |           Non versioned |           2 |        100 |           5 |
+        |               Versioned |           2 |        100 |           2 |
+        |               Suspended |           2 |        100 |           2 | 
+
     @2.7.0
     @PreMerge
     @Flaky