From 237e39612b7cf2ebae4f01ee459ac36b87ae8870 Mon Sep 17 00:00:00 2001
From: Simon <simon.dumas@protonmail.com>
Date: Thu, 15 Aug 2024 10:41:52 +0200
Subject: [PATCH] Fix log when updating content type in S3 in ship (#5104)

Co-authored-by: Simon Dumas <simon.dumas@epfl.ch>
---
 .../scala/ch/epfl/bluebrain/nexus/ship/files/FileCopier.scala | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ship/src/main/scala/ch/epfl/bluebrain/nexus/ship/files/FileCopier.scala b/ship/src/main/scala/ch/epfl/bluebrain/nexus/ship/files/FileCopier.scala
index d52ca6e52f..5e50cff369 100644
--- a/ship/src/main/scala/ch/epfl/bluebrain/nexus/ship/files/FileCopier.scala
+++ b/ship/src/main/scala/ch/epfl/bluebrain/nexus/ship/files/FileCopier.scala
@@ -78,8 +78,8 @@ object FileCopier {
           case CopyResult.AlreadyExists =>
             IO.whenA(forceContentType) {
               attributes.mediaType.traverse { mediaType =>
-                logger.info(s"Patching to content type $mediaType for file $patchedFileName")
-                s3StorageClient.updateContentType(targetBucket, targetKey, mediaType)
+                logger.info(s"Patching to content type $mediaType for file $patchedFileName") >>
+                  s3StorageClient.updateContentType(targetBucket, targetKey, mediaType)
               }.void
             }
         }.timed