I think packaging only works for pure Flux code, if you added a custom function written in Go you either need to submit a PR or provide your customer with a build from your fork.
That is possible for sure. On the other hand Flux code base cannot be polluted with every customer specific extension, while customers will likely insist on using official distribution.
I was thinking that a mechanism similar to external plugins in Telegraf 1.12+ (Go plugin feature) could be used for Go functions in a user package.
We’ll start work on the package manager and user packages later this year, likely in April or so with it available shortly after that. However, that’ll only be useful for pure Flux functions. For the stuff you’ve written in Go, can you share what it is? I’m wondering if there’s a way to represent that in pure Flux.
@pauldix The function in Go calculates a set of geohashes which covers specified lat/lon box area and the resulting set is used as contains() parameter in filter() like