Sometimes set irrelevant parameter in repo analysis tests

Author: DaveCTurner

x-pack/plugin/snapshot-repo-test-kit/qa/s3/src/javaRestTest/java/org/elasticsearch/repositories/blobstore/testkit/analyze/S3RepositoryAnalysisRestIT.java

@@ -112,7 +112,14 @@ protected Settings repositorySettings() {
             .put("delete_objects_max_size", between(1, 1000))
             .put("buffer_size", ByteSizeValue.ofMb(5)) // so some uploads are multipart ones
             .put("max_copy_size_before_multipart", ByteSizeValue.ofMb(5))
-            .put(randomFrom(Settings.EMPTY, Settings.builder().put("add_purpose_custom_query_parameter", randomBoolean()).build()))
+            // verify we always set the x-purpose header even if disabled for other repository operations
+            .put(randomBooleanSetting("add_purpose_custom_query_parameter"))
+            // this parameter is ignored for repo analysis
+            .put(randomBooleanSetting("unsafely_incompatible_with_s3_conditional_writes"))
             .build();
     }
+
+    private Settings randomBooleanSetting(String settingKey) {
+        return randomFrom(Settings.EMPTY, Settings.builder().put(settingKey, randomBoolean()).build());
+    }
 }