influxdata / influxdata/influx-cli
Make creating configurations easier
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 75
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Proposal:
Make the influx config create command interactive for parameters not passed as flags
Current behavior:
You must pass all config parameters as command line arguments, which requires knowing what arguments you need
Desired behavior:
A user should be able to run influx config create alone and be promoted to input each config parameter.
Alternatives considered:
You could allow a mix of command line arguments and interactivity, only prompting for what wasn't passed on the CLI.
You could also check for environment variables to use as default options in the interactive mode.
Use case:
Using configurations is the new recommended way to use the influxdb CLI, but the process for creating them is not clear or intuitive, which will leave new users feeling confused by InfluxDB and having an undesirably high "time to awesome"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the influx config create command entry point and determine how its current required parameters are defined and collected. Compare interactive prompting with the proposed mixed flag-and-prompt and environment-variable alternatives; done means running influx config create without flags prompts for each required configuration parameter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100