Replies: 1 comment
-
|
Hi @gedw99, thanks for posting!
Do you mean that you can't (or don't want to) use gomplate without a feature like this? Or is there a specific use-case where you're running into trouble because gomplate doesn't work like this? My gut feeling is that this isn't something that should be a gomplate feature, but perhaps some kind of wrapper program. The problem of "watching" a datasource in the generic sense could be solved through periodic polling, but this can be quite inefficient especially over time. For datasources on the local filesystem maybe a program like air is enough. But other than polling, how would you discover when a Vault datasource has updated? Or HTTP? Or S3? There are some more efficient mechanisms - some OSes have Some of the templates that I've written are involved in various software development activities, where I have a Makefile present already. So an approach that I take there is to have a target for the templated file that depends on the datasource files. Then, whenever I run For a concrete example, see this target that updates the Does this make sense? Am I misunderstanding your goal? |
Beta Was this translation helpful? Give feedback.
-
It feels like data source watchers are the missing part.
When the data source changes , run any template linked to that data source…. It’s not quite that simple but that’s the goal.
ghis whole watching is sometimes called CDC. A change is empressed and then a template can react. create, update , delete are the Op Types. A different template would typically be run based on the Op Type.
I was wondering if there are any recommendations ?
Beta Was this translation helpful? Give feedback.
All reactions