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.

Sign up for GitHub

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

Jump to bottom

Introduce an explicit upgrade command #367

Closed
jstuczyn opened this issue Oct 8, 2020 · 0 comments · Fixed by #381
Closed

Introduce an explicit upgrade command #367

jstuczyn opened this issue Oct 8, 2020 · 0 comments · Fixed by #381
Assignees
@jstuczyn
Labels
enhancement New feature or request
Projects
Core systems
Milestone
0.9.0

Comments

@jstuczyn
Copy link
Contributor

jstuczyn commented Oct 8, 2020

Each time we release a new version, people are running init again and blowing their existing config values.
upgrade should instead re-init your configs but read old values first.
@jstuczyn jstuczyn added the enhancement New feature or request label Oct 8, 2020
@jstuczyn jstuczyn added this to the 0.9.0 milestone Oct 8, 2020
@jstuczyn jstuczyn added this to Backlog in Core systems via automation Oct 8, 2020
@jstuczyn jstuczyn mentioned this issue Oct 12, 2020
Closed
@jstuczyn jstuczyn self-assigned this Oct 12, 2020
@jstuczyn jstuczyn mentioned this issue Oct 13, 2020
Merged
Core systems automation moved this from Backlog to Done Oct 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jstuczyn jstuczyn

Labels
enhancement New feature or request
Projects
Core systems
Archived in project
Core systems
  
Done
Milestone
0.9.0
Development

Successfully merging a pull request may close this issue.

Feature/upgrade command nymtech/nym
1 participant
@jstuczyn