influx CLI release notes
This release includes two new bug fixes.
Improve error messages for unknown subcommands (
Error: command “…” not recognized.) by describing how to run
./influx --helpto see a list of valid commands. Thanks @slai!
org members removeAPI calls successfully remove a member from an organization by fixing accidental swap of
userID. Thanks @geek981108!
This release includes three new features and bug fixes.
This release makes it easier to create API tokens with the
influx CLI, adds support for viewing more than 20 buckets using
influx bucket list, and adds a shorthand flag for bucket (
Create an Operator token in the influx CLI
Add the ability to use the
influx CLI to create an Operator token with read and write permissions to all resources in all organizations available in InfluxDB. (Note, this is the same permissions generated for the initial token created by
influx setup or
Create an All-Access token in the influx CLI
Add the ability to use the
influx CLI to create an All-Access API token with read and write permissions to all resources in an organization.
View more buckets in the influx CLI
influx bucket list with pagination to support displaying more than 20 buckets. By default, buckets are fetched in batches of 20; set
--page-size to override this default value. You may also limit the total number of buckets to display with
--limit (by default, there’s no limit).
New bucket shorthand for influx delete
Add the shorthand flag
- Detect and warn when the Operator token is changed using
influx restore(either setting a new
--activeconfig or updating the
- Set newly-created connection configuration as active in
- Embed timezone data into Windows builds to avoid errors.
Upgrade to Go 1.17.
- Fix shell completion for top-level
- Make global
--http-debugflag visible in help text.
- Don’t set empty strings for IDs in permission resources.
- Detect and error out on incorrect positional arguments.
- Respect value of
--hostflag when writing CLI configs in
This is the initial release of the
influx CLI from the
influxdata/influx-cli GitHub repository.
influx write skip-header parsing
To simplify the CLI parser, the
write command no longer supports
as short-hand for
Stricter input validation for
influx template commands
stacks commands now raise errors when CLI options fail to parse instead of silently discarding bad inputs.
This change was made to help users debug when their commands fail to execute as expected.
Server-side template summarization and validation
template validate commands now use an API request to the server to perform their logic, instead of performing the work on the client-side.
Offline summarization and validation is no longer supported.
This change was made to avoid significant code duplication between
influx CLI, and to allow server-side template logic to evolve without requiring coordinated CLI changes.
influx stacks --json output conventions
The output of
influx stacks --json previously used an UpperCamelCase naming convention for most keys.
The command now uses lowerCamelCase consistently for all objects keys, matching the schema returned by the API.
- Add global
--http-debugflag to all
influxcommands to help inspect communication with InfluxDB servers.
bucket createto allow setting a schema type.
bucket listto display schema types.
--skip-verifyflag to the
- (InfluxDB Cloud only) Add [`buck
- (InfluxDB OSS only) Updates to
- (InfluxDB OSS only) Add
user passwordcommand to allow bypassing interactive prompt.
- Fix interactive password collection and color rendering in PowerShell.
org members listno longer hangs on organizations with more than 10 members.
- Detect and warn when inputs to
writecontain standalone CR characters.
dashboardscommand now accepts
--orgflag, or falls back to default org in config.
- Return a consistent error when responses fail to decode, including hints for OSS-only and Cloud-only commands.
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, use the following resources:
InfluxDB Cloud and InfluxDB Enterprise customers can contact InfluxData Support.