From fd974e1b79035d27521b1e1c7ab2cfc301c7f4ff Mon Sep 17 00:00:00 2001 From: Carlo Costino Date: Thu, 8 May 2025 16:54:50 -0400 Subject: [PATCH] Update no_proxy and S3 error handling This changeset updates the no_proxy environment variable to allow S3 through. It also updates our error handling connecting to S3. Signed-off-by: Carlo Costino --- .profile | 2 +- app/aws/s3.py | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.profile b/.profile index 56bce7385..c6fb0b05f 100644 --- a/.profile +++ b/.profile @@ -6,4 +6,4 @@ export http_proxy=$egress_proxy export https_proxy=$egress_proxy export NEW_RELIC_PROXY_HOST=$egress_proxy -export no_proxy="apps.internal" +export no_proxy="apps.internal,s3-fips.us-gov-west-1.amazonaws.com" diff --git a/app/aws/s3.py b/app/aws/s3.py index bc1728541..3b9eafa89 100644 --- a/app/aws/s3.py +++ b/app/aws/s3.py @@ -116,9 +116,9 @@ def list_s3_objects(): ) else: break - except Exception: + except Exception as e: current_app.logger.exception( - "An error occurred while regenerating cache #notify-debug-admin-1200", + f"An error occurred while regenerating cache #notify-debug-admin-1200: {str(e)}", )