Comments below. On Mon, Feb 13, 2023 at 11:44 AM Proven Provenzano <pprovenz...@confluent.io.invalid> wrote: > > Hi Jose > > I want to clarify that the file parsing that Argparse4j provides is just a > mechanism for > taking command line args and putting them in a file. It doesn't > actually change what the > command line args are for processing the file. So I can add any > kafka-storage command > line arg into the file including say the storage UUID. I see that the file > parsing will be useful > in the future as we add more record types to add for the bootstrap process.
Understood. > I'm against adding specific parsing for a list of configs vs. a separate > JSON file as it is adding > more surface area that needs testing for a feature that is used > infrequently. One config method > should be sufficient for one or more SCRAM records that a customer wants to > bootstrap with. Does this mean that the storage tool won't parse and validate SCRAM configuration? How will the user know that their SCRAM configuration is correct? Do they need to start the cluster to discover if their SCRAM configuration is correct? Thanks, -- -José
