Open weissne opened 2 months ago
Thanks for your suggestion! Can you specify which filesystem events that trigger the callback at the moment you are trying to avoid?
Thanks for your response.
Sorry for not clarifying this, but I'm not trying to avoid filesystem events that trigger the callback now. The idea here is to enable, in addition to the existing "Moved" filesystem event that is watched and triggers a callback, also the watch of "Modified". We need this because the "Modified" filesystem event is triggered, instead of "Move", when certificates are updated in our monitored "path_config_source" defined for our Secrets, because of the way it's done, which we don't have control over.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
@adisuissa - Can you please share your thoughts on this following my clarifcation? I would be happy to implement this if possible.
Accidently closed the issue :) Reopening...
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
Apologies for the late reply. This is by design. See https://github.com/envoyproxy/envoy/issues/20474#issuecomment-1075855325
Title: Add optional support for watching for "Modified" filesystem events
Description:
The field will be optional and only when set to true will the Modified filesystem event be accepted by the watcher and will trigger it's callback.