-
-
Couldn't load subscription status.
- Fork 431
Add Delete command to gRPC #2212
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
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #2212 +/- ##
==========================================
+ Coverage 62.95% 62.99% +0.03%
==========================================
Files 220 220
Lines 19478 19496 +18
==========================================
+ Hits 12263 12281 +18
Misses 6132 6132
Partials 1083 1083
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
d57d41f to
6ade5da
Compare
6ade5da to
d74352b
Compare
d74352b to
9ae9461
Compare
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.mdhas been updated with a migration guide (for breaking changes)configuration.schema.jsonupdated if new parameters are added.What kind of change does this PR introduce?
Code enhancement
What is the current behavior?
It is not possible to entirely remove a key from the config file using the gRPC interface. Setting it to an empty object using either
MergeorSetValuewould not work because viper would set it back to its default value, which is the one written in the config when it was loaded.The only workaround would be to set the nested key to empty objects using the above mentioned commands:
What is the new behavior?
The key can be deleted from the runtime configuration using the
Deletecommand.Does this PR introduce a breaking change, and is titled accordingly?
No