The apicast-logger from nmasse-itix

apicast-logger's Introduction

Nicolas Massé

🚀 Coder, Architect, Geek. 🚀

👨‍👧 Guardian of the Future: Embarks on life's greatest adventure as the proud dad of a 4-year-old little explorer, teaching her the ways of the Force and the magic of code.
🎮 Tech Enthusiast: 17 years journeying through the dungeons of containerization, DevOps, security, and Edge Computing.
🛠 Craftsman of Code: Wields Go like a legendary sword, shapes Open Source to forge a secure & sustainable digital future.
🗣 Wizard of Conferences: Unveils his spells at Red Hat Summit, Devoxx France, lighting the dark paths of DevOps and Security.
🧩 World Builder: Assembles Lego Technic with the precision of a Swiss clockmaker, in a perpetual quest for excellence.
🌍 Digital Explorer: Maps his technological saga on itix.fr and reveals his code artifacts on github.com/nmasse-itix.

🌟 Join his expedition across the galaxies of code and innovation on GitHub! 🌌

apicast-logger's People

Contributors

Stargazers

Watchers

apicast-logger's Issues

Convert to new APIcast policy chain

APIcast 3.2 is going to have a policy chain - multiple policies chained together.

That means policies do not have to be aware of the 'apicast' module and multiple policies can be enabled at the same time.

The documentation is a bit scarce but your feedback on what is missing could be really helpful for us.
We've converted existing CORS example into a new policy: 3scale/APIcast#487

I'm happy to help how to make the setup so it is easy to test and develop.

Update this module so that it can work with Apicast 3.1

Latest version of Apicast work differently for DNS name resolution. See 3scale/APIcast#324.

Namely, on version 3.1, the module produces this error message:

Nov  7 21:24:42 ip-172-31-31-249.us-east-2.compute.internal dockerd-current[2843]: 2017/11/08 02:24:42 [error] 30#30: *685 [lua] verbose.lua:92: do_log(): failed to log message: try to send log messages to the log server failed after 3 retries: try to connect to the log server failed after 3 retries: no resolver defined to resolve "ec2-52-14-196-66.us-east-2.compute.amazonaws.com" while sending to client, client: 172.17.0.1, server: _, request: "GET /?user_key=d07cc438281c2f088ff72a665870d559 HTTP/1.1", upstream: "https://107.23.177.9:443/?user_key=d07cc438281c2f088ff72a665870d559", host: "echo-api.3scale.net"

It seems that we now have to use the RESOLVER environment variable instead of the resolver directive in the nginx configuration file.

Recommend Projects