thanks for the reply, in our environment - all of the commands I listed above work in our qa/pre-prod/stageing/production -dr, and production environments but in DEV (the systems im seeing the errors) they do NOT work
here are some example running the cli and curl commands above on different environments in our Datacenter
Production DR:
CLI:
vault-2:~$ vault list secret/config
Keys
api-gateway,production-dr
appointment-service,production-dr
billing-adapter,production-dr
billing-event,production-dr
(there are over 200 more entries i didn’t list but you get the idea)
and if I curl against that environment
CURL:
curl -H “X-Vault-Token: XXXXXXXXXXXXXXXXXXX” -X LIST https://vault-1.my-production-dr.com:8200/v1/secret/config
{“request_id”:“7186164c-3958-af44-a0d6-f4fe173801b2”,“lease_id”:"",“renewable”:false,“lease_duration”:0,“data”:{“keys”:[“api-gateway,production-dr”,“appointment-service,production-dr”,“billing-adapter,production-dr”,“billing-event,production-dr”,
again several pages of output
The reason for this troubleshooting is that users were able to add K/V items to the secret/config from the UI until a few days ago - there are about 290 entries in this secret currently - all manually entered through the UI over the past few years, then this error started happening and they passed it off to me 
again all command (cli and curl) i posted above work in 5 environments - but NOT in the 6th - The only difference in all of the environments is process - they are all physically identical accept developers have root access to the dev cluster - and NO access to the others
So my thought is that someone “broke it” i don’t know how (why im here) just trying to fix it