pulsar standalone docker image should support initialization of some kind

[flowchartsman]

This would be very useful for development and integration testing. Currently have to run a parallel container calling pulsar-admin in a loop to wait on the relevant endpoints to be up and spin up the tenants/namespaces/policies that I need to simulate my deployment environment.

Perhaps this could be read from a file at a known location and then spun up in place fo the sample tenant/namespaces if it's found?

[flowchartsman]

My suggestion would be something like the following:

1. before spinning up the admin endpoint, look for a file in a known location (following mongo's example, this would be something like /docker-entrypoint-init.d/pulsar-init
2. If this file is found, process it
3. otherwise, proceed with sample tenant/namespace creation

As for the format of the file, one option would be to simply treat it as a newline-separated list of arguments to pulsar-admin invocations:

tenants create test
namespaces create test/admin
namespaces create test/news
namespaces create test/emails
namespaces set-retention --size-1 --time 3d test/news
namespaces set-publish-rate -m 10 test/emails

[tisonkun]

Moved to the General Discussions forum. I like the idea but it requires a design and volunteers working on it. Discussions forum is sorted default by updated and gives this thread more attention.

Perhaps .hiverc to Hive. For your suggestion command pattern, the problem is which bin script to execute, shall we support run bin/pulsar ... also?