Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot get version of influx CLI #14821

Closed
gitirabassi opened this issue Aug 27, 2019 · 7 comments · Fixed by #18344
Closed

cannot get version of influx CLI #14821

gitirabassi opened this issue Aug 27, 2019 · 7 comments · Fixed by #18344

Comments

@gitirabassi
Copy link
Contributor

Probably is hidden in the code but neither influx --version, influx version, influx -v and when executing influx --help there is no mention on how to output a version

@kelwang
Copy link
Contributor

kelwang commented Sep 17, 2019

@gitirabassi you are talking about the influxdb version, not the cli version, right?

@gitirabassi
Copy link
Contributor Author

I was asking for the CLI, but both would be awesome. When I was running it, i wasn't sure if running the v1 or v2 version of the client.

My primary concern is with people migrating from v1

Also, would be cool to have, other then the version of the server, some metadata of it: if cloud, enterprise or OSS.

These down here are docker and kubernetes examples. I would be fine with a 2 liner to start with

bash-3.2$ kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-30T12:22:52Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.10", GitCommit:"37d169313237cb4ceb2cc4bef300f2ae3053c1a2", GitTreeState:"clean", BuildDate:"2019-08-19T10:44:49Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}
bash-3.2$ docker version
Client: Docker Engine - Community
 Version:           19.03.2
 API version:       1.40
 Go version:        go1.12.8
 Git commit:        6a30dfc
 Built:             Thu Aug 29 05:26:49 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.2
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.8
  Git commit:       6a30dfc
  Built:            Thu Aug 29 05:32:21 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

@jsteenb2 jsteenb2 self-assigned this Sep 25, 2019
@stale
Copy link

stale bot commented Dec 24, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Dec 24, 2019
@gitirabassi
Copy link
Contributor Author

I don't think this should be closed yet!

@stale stale bot removed the wontfix label Dec 26, 2019
@jsteenb2
Copy link
Contributor

agreed!

@jsteenb2 jsteenb2 removed their assignment Jan 2, 2020
@imogenkinsman
Copy link
Contributor

A version command was added for influxd by #15629, but it would still be good to have a version command for the CLI (which would display the version of the client).

@kelwang kelwang self-assigned this Apr 2, 2020
@jsteenb2
Copy link
Contributor

jsteenb2 commented Jun 2, 2020

@gitirabassi ws talking with @russorat about our versioning. We can do something similar to clickhouse, where you run version, it reaches out to the server in the config, and lets the user see both the client version and the server version. WDYT?

reference: https://clickhouse.tech/docs/en/interfaces/cli/#command-line-client

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants