Open randomsync opened 1 week ago
@randomsync is this going to roll over?
The older configs for staging were removed on 9/18. While testing, I noticed that we're seeing this error:
<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
</body>
</html>
: {:uuid=>"71b9a678-05d9-4c1e-8d68-f6e859d8e81e"}
I don't think these are related to the config removal, but just to be double sure, we'll need to dig into this and confirm 100% that they are not related, before we remove the older configs for production. Currently, the production travel claims are working fine.
for reference, here are the older configs that need to be removed: https://console.amazonaws-us-gov.com/systems-manager/parameters/?region=us-gov-west-1&tab=Table#list_parameter_filters=Name:Contains:%2Fdsva-vagov%2Fvets-api%2Fprod%2Fcheck_in%2Fbtsss
just tried to make a request through fwd-proxy in staging through insomnia and got a connection refused. so this might be an issue with fwdproxy in staging. will work with devops team to debug
The older v1 configs for BTSSS have been removed from:
This ticket is to remove those configs from AWS param store.