I’ve taken the liberty of moving this PM to a topic as the response should be of general interest, especially to influxDB1 (and influxDB2) users.
I’ve read over the docs for influxDB3. It seems to be true that influxDB3 only requires changing the authorization from “Basic” to “Bearer”. That is included in a header and would be easy to change.
However:
While the write protocol remains identical, the support of influxQL is billed as transitional support and not guaranteed to be supported forever. I don’t know how they would be able to desupport something like that but then again they pushed influxDB2 on the community with the disastrous FLUX query.
So if I’m going to code up support for this third go-round, I would move to the native SQL query to resolve last post on startup. That will require a little work, but actually quite a bit cleaner. As I understand it influxQL is a compatibility layer on top of the SQL query anyway.
So bottom line is that it looks pretty doable. Right now I’m finishing up with @brettbeeson on his contributed PostgREST uploader which is essentially done, just testing and integration. After that, I’ll stand up an influxDB3 instance and add support.