chore: pnpm fix config bucket s3 locale (#1177)

Fix du problème de pièces jointes suite au changement pnpm
communication node => docker

Author: l-scherer

.env.dev.example.env

@@ -73,9 +73,9 @@ ANTIVIRUS_URL="https://antivirus.fabrique.social.gouv.fr/vao/api/v1/scan"
 # S3 config to use with minio in local
 S3_BUCKET_ACCESS_KEY=minioadmin
 S3_BUCKET_SECRET_KEY=minioadmin
-S3_BUCKET_ENDPOINT="http://minio:9000"
+S3_BUCKET_ENDPOINT=http://localhost:9000
 S3_BUCKET_NAME=vao
-S3_BUCKET_REGION=xxx # do not matter with minio
+S3_BUCKET_REGION=us-east-1
 S3_BUCKET_ROOT_DIR=local
 
 DEBUG=*debug*

.talismanrc

@@ -1,6 +1,6 @@
 fileignoreconfig:
 - filename: .env.dev.example.env
-  checksum: 214ed60bba95f8959eecc3555a83ca7b9fde3598e19e8ee4c61d0a5f1cc2c197
+  checksum: 217ba7248908d2556647f3e315d96faa67baa36cb19d90e998d4dc6121dcf648
 - filename: .github/workflows/e2e.yaml
   checksum: d28e325635cc8d77cbf5b260c67cb9721b58578ac86ddd39ec691e753e4d0412
 - filename: .github/workflows/lint-format-tests.yaml

docker-compose.yaml

@@ -64,5 +64,6 @@ services:
       - S3_BUCKET_ACCESS_KEY=${S3_BUCKET_ACCESS_KEY}
       - S3_BUCKET_SECRET_KEY=${S3_BUCKET_SECRET_KEY}
       - S3_BUCKET_NAME=${S3_BUCKET_NAME}
+      - S3_BUCKET_REGION=us-east-1
     depends_on:
       - minio