Create new functions to export to influx2

[breadlysm]

Likely will need to refactor Influx1 exporter.

possible solution
Lean functions that handle common tasks in influx class.
Inherit those into separate objects for influx 1 and 2.

another option is just separate connection methods for 1&2 with separate exports under the same object.

[andrema2]

Hi, I really like your work. Do you have any time frame for when Influxdb2 connection would be ready ? I see it closed, but no new ENV variables and so on.
Thanks

[marty-oehme]

@andrema2 Over summer I quickly threw together a version of this project that works with InfluxDBv2 here, be aware that it's based on a very old version of this codebase though.

[mrkirbyv]

There is still a V1 endpoint in V2 that works with the identical POST except that you have to add an Auth token header to the POST. That might be the easiest way to get it to work with V2 without much internal work. Just add an env for the token and use it to create an additional header. All else stays the same.