-
Notifications
You must be signed in to change notification settings - Fork 822
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
Config: Add versioning #1671
Config: Add versioning #1671
Conversation
70797f0
to
3d955f8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good stuff. Will give it a thorough testing next round. Thanks.
522cb73
to
e8546a6
Compare
@shazbert I'm done restructuring this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice changes! Thanks for changing the requested. Also just mentioning config_example.json can we now shift that up in line with this versioning system, I see you have commited the configtest.json file.
See PR description 🙂
The test config I could upgrade without introducing any new nulls. I know I could fix those, or run a whole instance on it to get them fixed, but I want to use it as a test case for making sure our fully versioned upgrade path handles all the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks sir, just a diff with changes that needs to be added then looks good to go after merge with master. Nice work!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Nothing else from me.
a35693a
to
02b027d
Compare
Rebased. I've dropped out the "upgrade test config" change. I've realised that I should work through moving all of the things that trigger warnings to proper versions first, then it won't even matter. That's pretty trivial but I'll let this land as-is first. The method to upgrade it is to run config tool with upgrade, then remove anything that would be nulled out. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1671 +/- ##
==========================================
+ Coverage 37.04% 37.12% +0.07%
==========================================
Files 414 418 +4
Lines 180305 180303 -2
==========================================
+ Hits 66800 66941 +141
+ Misses 105657 105497 -160
- Partials 7848 7865 +17
|
02b027d
to
fff95a1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm excited for config versioning. Just did some light prodding
23abfa0
to
1b498f3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the latest updates. One main thing I encountered before continuing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One nit others are commentary. Nice work!
dbb9635
to
8181ec3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ch ACK! Thank you 🖖
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested everything and looks to all be good aside from a basic issue. Great work on this feature!
c568878
to
82e885c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making those changes! Just some remaining minor consistency issues and then this looks good to go!
This restructure allows us to share types between versions, avoids needing to import the versions, and puts the test fixtures in same package. It's a win on all fronts
Called from engine before logger is inited, and also just wrong to use log to communicate with user
Checking the versions at Deploy is much saner.
This simplifies the handling for encryption prompts by moving it to a field on config, allowing us to simplify all the places were were passing around config Also moves password entry to being secure (echo-off)
6709cf7
to
262c5d3
Compare
Rebased and squashed following last fixes, which were cosmetic. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tACK, nice work 🚀
Config
Note Well: The test failure in
TestConfigAllJsonResponse
is fixed by the dependency belowDependencies
TestConfigAllJsonResponse
Type of change