Those path lists are legacy and they shouldn’t be as we stopped supporting in version 2 I think
As for the second error, I haven’t encountered that before. You may want to check your app path value is correct or that there are no read or write restrictions in that part. Or that the api_id of your definition does not have any whitespace or unicode characters
The legacy path issue was solved with your comment. Thanks a lot!
I’ve been trying to debug the other error and see if there are any read or write restrictions on the files but I can’t find anything. I’ve deployed with the official helm chart for the headless version of the Tyk Gateway.
I’m attempting to mount some api definitions as json files from a config map at start up and copy them into the container in an init container step. The path I’m copying the files over to is mnt/tyk-gateway/apps.
It’s working fine and the api definitions are loaded. However I see the above error
gateway-tyk-headless time="Mar 27 17:19:49" level=info msg="Loading API Specification from /mnt/tyk-gateway/apps/graphql-service.json" gateway-tyk-headless time="Mar 27 17:19:49" level=error msg="error while closing file /mnt/tyk-gateway/apps/graphql-service.json"