errose28 commented on PR #7170:
URL: https://github.com/apache/ozone/pull/7170#issuecomment-2347130491
We had some discussion on this and came up with the following points:
- It will be useful to have a command `ozone ratis` that works the same as
the `ratis` CLI, but automatically populates the TLS information required to
communicate with a secure Ozone cluster.
- Currently `ratis` invoked from the command line does not support TLS and
will fail.
- We should implement this in a way where Ozone can just forward arguments
to Ratis. We should not manually create wrappers of the same names for every
Ratis CLI, like how this change is currently implemented.
- One possible solution proposed by @szetszwo was a Ratis change that
exposes `RatisShell` and allows passing a builder for TLS configuration. Then
from the `ozone ratis` subcommand we could do something like this:
```java
RatisShell shell = new Builder().setTlsConf(tls).build();
shell.run(args)
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
