Conversation
|
Hey @Dinnerbone, I pulled this PR and gave it a good test (per samwiseg0's request in the Discord server) and it seems to work just fine with Influx v2.3+. I built a docker image with it and it successfully deployed and was able to communicate with Influx v2 via an org owner account. A varken bucket was created and it was able to send data to the bucket. Which could be loaded in a barebones flux dashboard in Influx and Grafana. 👍 The only real issue(?) I can see would be not having token-based auth available for v2 (sort of like #195). Which would be great for single org Influx setups. I don't know if it would be easy to just have a |
I am ok with adding another option even if it is specific to v2 |
|
Just curious, is anyone with merge permission ever going to gather up all the recent info on this and coherently merge these pull requests into master? |
|
you have some issues T23:38:08Z', 'ratings': {'votes': 0, 'value': 0}, 'languageProfileId': 1, 'id': 523}, 'grabbed': False, 'id': 82641} |
|
@NOXITB and what leads you to believe that the problem is in this PR? |
An alternative approach than #195
We use v2 API everywhere except for the creation of a database on 1.8 servers. The same config keys are used, but with a new "org" key for v2 servers.