IoannisRP
IoannisRP
changes in [force-push](https://github.com/redpanda-data/redpanda/compare/2066dc1451f1044f566896f635bb3d0e43029c27..4c1a4ebdec0c4efcdd6bc62235f4487aec26e958): - centralize all password-length checks
changes in [force-push](https://github.com/redpanda-data/redpanda/compare/4c1a4ebdec0c4efcdd6bc62235f4487aec26e958..32370f783b98d234f022a55d73107908c5c82b8d): - add documentation to new length-checking functions changes in [force-push](https://github.com/redpanda-data/redpanda/compare/32370f783b98d234f022a55d73107908c5c82b8d..50e5e9ea7c6d3735565cb23fd11617256f8e9b23): - rebase to dev
> The issue is that brokers may shut down and come back and in that time they'll lose the ephemeral credentials they previous held, so we need to react to...
> FYI regarding commits, see: https://github.com/redpanda-data/redpanda/blob/dev/CONTRIBUTING.md Are you referring to the follow up changes? I am going to rebase and squash these in the end. Or is it something else?
@travisdowns > Not sure if it makes sense to fix upstream seastar first or at all? Fragmentation is real for seastar users in general so they are more or less...
Added lifetime-management precondition comment for `FutureRange`.
CI failures: - PR #23834 - PR #23836 - [CORE-7839](https://redpandadata.atlassian.net/browse/CORE-7839) - [CORE-7957](https://redpandadata.atlassian.net/browse/CORE-7957) [CORE-7839]: https://redpandadata.atlassian.net/browse/CORE-7839?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ [CORE-7957]: https://redpandadata.atlassian.net/browse/CORE-7957?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Updated commit message