-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Warning logs on environment read in latest version #53
Comments
Hey! These warnings occur during the initialization phase or when a new configuration is received. The plugin attempts to resolve Datadog environment variable ( The warning is generated by kong.vault. Unfortunately, there isn't much I can do about it, aside from possibly using I apologize for not having a more satisfactory solution for you. I'll continue to brainstorm and see if I can come up with a better approach. |
@dmehala no problem. Adding one more thing: So, if someone tries to set these variables in a new prefix(as I was trying to get rid of the warnings), this plugin does not support a custom path for it, so it won't work. |
could the plugin be made to not be configurable by env var and defer that to the user to use env vars in their config / deck yaml file? I dont know of any other plugin that makes direct calls to get_env(), it seems like this possibly isn't intended to be used by external code?
Thanks for pointing to this. Just to add, its then every 1min after that as I believe kong is doing it own secret rotation |
Kong Version
3.6.1
Plugin Version
0.2.0-1
On which environment your Kong instance is running?
ECS
Plugin Configuration
What happened?
Within this latest version, I'm getting several warning logs from the plugin about errors on reading the env configs from a vault:
I don't even have a vault configured within this Kong.
This is not impacting the availability of the Kong Gateway, but it's a very verbose log that's being triggered all the time.
The text was updated successfully, but these errors were encountered: