Is your feature request related to a problem? Please describe.
Having to run ksqldb server in headless mode so it will pick up queries file that will create streams and tables but then applications are unable to run Select statements because REST interface is disabled.
Describe the solution you'd like
As I understand, specifying a queries file to the ksqldb server makes it run in headless mode wherein it will run the commands in the file and then lock the server down from access (REST and CLI). What we are looking for is to able to provide queries file which will contain only DDL or DML (Create, Insert statement) and still have the server run in a 'restricted interactive' mode wherein only dql (Select statement) commands can be executed and definitions are left intact.
Is your feature request related to a problem? Please describe. Having to run ksqldb server in headless mode so it will pick up queries file that will create streams and tables but then applications are unable to run Select statements because REST interface is disabled.
Describe the solution you'd like As I understand, specifying a queries file to the ksqldb server makes it run in headless mode wherein it will run the commands in the file and then lock the server down from access (REST and CLI). What we are looking for is to able to provide queries file which will contain only DDL or DML (Create, Insert statement) and still have the server run in a 'restricted interactive' mode wherein only dql (Select statement) commands can be executed and definitions are left intact.
Describe alternatives you've considered This is also a good alternative: https://github.com/confluentinc/ksql/issues/5484
Additional context N/A