I restarted the gateway, see nothing about downloading the bundle.
I hit the API endpoint and just get a failure as the API is dependent on an custom Auth Plugin auth header that the middleware should be setting, but it is not, because I don’t see any evidence that its being pulled, installed and used by the API.
This middleware works fine, when not in a bundle, and just referenced locally on the gateway via the normal custom_middleware block
I then logged into the container (gateway) and manually created the middleware/bundle directory (why do I have to do this?)
Restarted gateway and now the previous error above is gone, but now these new ones. (note the container runs as root so no idea why it could not or did not create that bundle directory on its own)
2017-08-07T14:58:32.776748541Z time=“Aug 7 14:58:32” level=info msg="----> Loading bundle: my-bundle.zip"
2017-08-07T14:58:32.776788593Z time=“Aug 7 14:58:32” level=info msg="----> Verifying bundle: my-bundle.zip"
2017-08-07T14:58:32.777200804Z time=“Aug 7 14:58:32” level=info msg="----> Bundle is valid, adding to spec: my-bundle.zip"
2017-08-07T14:58:32.777237061Z time=“Aug 7 14:58:32” level=error msg=“Failed to load Middleware JS: read middleware/bundles/ba2c643525a54dc34b975179a7d9f12a-my-bundle.zip: is a directory”
2017-08-07T14:58:32.777260533Z time=“Aug 7 14:58:32” level=error msg=“Failed to load Middleware JS: read middleware/bundles/ba2c643525a54dc34b975179a7d9f12a-my-bundle.zip: is a directory”
If I shell into the gateway I do see this directory