[FOLIO-3313] Introduce/verify ENV vars for mod-data-export Created: 15/Oct/21  Updated: 16/Nov/21  Resolved: 21/Oct/21

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Story Priority: P2
Reporter: Viachaslau Khandramai (Inactive) Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-3310 Data export jobs get stuck on the fol... Closed
Sprint: DevOps Sprint 125
Development Team: FOLIO DevOps

 Description   

Purpose:

According to the last changes in mod-data-export configuration ( MDEXP-445 Closed - Improve MinIO configuration process)  one need to make the following changes on hosted reference env (folio-testing, folio-snapshot and others):

1) Remove JAVA_OPTIONS: -Daws.url, -Daws.region, -Daws.accessKeyId, -Daws.secretKey, -Dbucket.name.

2) Instead of JAVA_OPTIONS introduce/verify ENV variables: AWS_URL, AWS_REGION, AWS_BUCKET, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY according to documentation https://github.com/folio-org/mod-data-export/blob/master/README.md#storage-configuration.

This story is improvement of previously implemented approach https://folio-org.atlassian.net/browse/FOLIO-3310

 



 Comments   
Comment by Wayne Schneider [ 20/Oct/21 ]

This change has been tested and merged. The overnight builds of the reference environments should contain the updated configuration.

Comment by Wayne Schneider [ 21/Oct/21 ]

Validated in folio-snapshot reference environment.

Generated at Thu Feb 08 23:27:11 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.