Skip to content
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.

CLI: enhance the config command experience #561

Closed
rugwirobaker opened this issue Oct 16, 2020 · 2 comments · Fixed by #674
Closed

CLI: enhance the config command experience #561

rugwirobaker opened this issue Oct 16, 2020 · 2 comments · Fixed by #674
Labels
core enhancement New feature or request

Comments

@rugwirobaker
Copy link

rugwirobaker commented Oct 16, 2020

Describe the solution you'd like

  • Adding the -all flag to config command which would print all the variables set in that project.(ALREADY IMPLEMENTED by config get)
➜  ✗ waypoint config get -all
  SCOPE | NAME | VALUE  
--------+------+--------
        | PORT     |  8000  
        | PASSWORD | password
        | USERNAME | username
        | .....    | .....
  • Also maybe a flag -raw to get the VALUES without the tabular format in case you want to pipe them to a file(.env)
➜ ✗  waypoint config get -all -raw | tee .env
PORT=8000  
PASSWORD=password
USERNAME=username
  • Another welcome feature would be to be able to pipe KEY/VALUE pair in the form of KEY=VALUE to the config set command
➜  ✗cat .env |  waypoint config set 

Describe alternatives you've considered
N/A

Explain any additional use-cases
N/A

Additional context
N/A

@mitchellh mitchellh added core enhancement New feature or request labels Oct 16, 2020
@mitchellh
Copy link
Contributor

These are all good suggestions.

For the first suggestion: what do you mean "all the variables set in that project" ? Is this not how waypoint config get behaves today? I'm sure I'm misunderstanding something here.

@rugwirobaker
Copy link
Author

Ohhh my bad I think it works.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
core enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants