-
Notifications
You must be signed in to change notification settings - Fork 592
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: update config descriptions to match docs #23347
Conversation
src/v/config/node_config.cc
Outdated
|
||
* Disabled - Redpanda does not start in FIPS mode. | ||
|
||
* Permissive - Redpanda performs the same check as enabled, but a warning is logged, and Redpanda continues to run. Redpanda loads the OpenSSL FIPS provider into the OpenSSL library. After this completes, Redpanda is operating in FIPS mode, which means that the TLS cipher suites available to users are limited to the TLSv1.2 and TLSv1.3 NIST-approved cryptographic methods. |
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.
- we try to line wrap around 80 columns
- maybe we need to maintain the nicely formatted version somewhere else?
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.
It would be awesome if we could move those messages to a message bundle of sorts.
@dotnwat @Deflaimun Can we get a status update please? |
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.
We do have some functionality problems caused by several changes within. Please see my comments for more details. briefly: any change that remains as a single line of text with no breaks will be accepted. Any multi-line doc strings cannot be accepted without a code change. let's work together on next steps.
src/v/config/node_config.cc
Outdated
"List of the seed servers used to join current cluster. If the " | ||
"seed_server list is empty the node will be a cluster root and it will " | ||
"form a new cluster", | ||
"List of the seed servers used to join current cluster. If the `seed_servers` list is empty the node will be a cluster root and it will form a new cluster. |
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.
Unfortunately, multi-line rich formatting like this will cause UX issues because we do output these strings in certain scenarios where we expect the string to be a one-line string.
@dotnwat and I had an idea that we could extend the C++ to have a _desc and a _longdesc member so that we could safely integrate really nice summaries like this into the product.
summary for today: any changes coming into this file need to be one-line strings. We'll need to follow up to accept larger blobs like this one. I'm happy to get on a call to help clarify what needs to change.
src/v/config/node_config.cc
Outdated
"Duplicate items in seed_servers: {}", *s_dupe_i); | ||
} | ||
return std::nullopt; | ||
std::sort(s.begin(), s.end()); |
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 don't think you meant to change this, looks like a formatter did it.
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.
Yes, that's correct.
src/v/config/node_config.cc
Outdated
"seed_servers list must be identical among those nodes' configurations, " | ||
"and those nodes will form the initial cluster.", | ||
"Controls how a new cluster is formed. All brokers in a cluster must have the same value. | ||
|
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.
even in cases like this, we don't want to have line breaks.
{.visibility = visibility::user}, | ||
{model::broker_endpoint(net::unresolved_address("127.0.0.1", 9644))}) | ||
, admin_api_tls( | ||
*this, | ||
"admin_api_tls", | ||
"TLS configuration for admin HTTP server", | ||
"Specifies the TLS configuration for the HTTP Admin API.", |
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.
changes like this are 100% compatible.
a36eec9
to
3c3b521
Compare
3c3b521
to
d65ae8c
Compare
|
d65ae8c
to
84bc7c6
Compare
@Deflaimun i've fixed the compilation error and formatting. lemme know if it looks ok. |
"form a new cluster", | ||
"`seed_servers` list is empty the node will be a cluster root and it " | ||
"will form a new cluster. When `empty_seed_starts_cluster` is `true`, " | ||
"Redpanda enables one broker with an empty `seed_servers` list to " |
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.
seed_servers
this isn't a big deal, but these strings really aren't intended to contain markdown, and i'm assuming that is what the backticks are for.
This comment was marked as outdated.
This comment was marked as outdated.
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/55693#01924fe1-764a-435b-b947-38510ef6ad66 ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/55693#01924fe1-7648-4d09-a62f-65df6414774f ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/55693#01924fe1-7644-44b7-a138-7d978b531e44 ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/55858#01925a75-3af4-44a6-a53c-49827dae27be |
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.
Having a poke with this over here: #23619
src/v/config/configuration.cc
Outdated
@@ -1190,7 +1299,7 @@ configuration::configuration() | |||
*this, | |||
"storage_max_concurrent_replay", | |||
"Maximum number of partitions' logs that will be replayed concurrently " | |||
"at startup, or flushed concurrently on shutdown.", | |||
"at startup, or flushed concurrently on shutdown. asdasdasdasdas", |
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.
👀
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.
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.
Oops, not sure how that got in there. Will remove! Thanks for the catch
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.
Fixed!
src/v/config/configuration.cc
Outdated
"Raft heartbeat RPC (remote procedure call) timeout. Raft uses a " | ||
"heartbeat mechanism to maintain leadership authority and to trigger " | ||
"leader elections. The `raft_heartbeat_interval_ms` is a periodic " | ||
"heartbeat sent by the partition leader to all followers to assert its " |
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.
The easy fix for the ducktape tests is to avoid the word "assert"
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.
should we reword to remove "assert" ? or are we writing an exception for these strings?
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 think we should add exceptions for these cases in ducktape. we don't want to restrict the language we can use in descriptions.
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 think we should add exceptions for these cases in ducktape. we don't want to restrict the language we can use in descriptions.
I agree, which is what I attempted here - but the NodeCrash regex still needs changing. I suggested an easy workaround.
I don't think the description of the config really needs to be rendered to the log at startup, the value should suffice.
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.
Please don't escape the %
(\%
), I count 4 of them.
84bc7c6
to
efe56d8
Compare
Force-push:
|
It doesn't lint anymore, the lines are too long. |
efe56d8
to
6577f4e
Compare
force-push: remove the word "assert" from description string. |
6577f4e
to
0b1ae30
Compare
The interesting diff between my review and now. |
Known CI Failures: Unknown (possible new)
|
Signed-off-by: Noah Watkins <noahwatkins@gmail.com>
Backfeed changes to configuration descriptions that were added to docs.
Backports Required
Release Notes
Improvements