You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/12/11 21:54:55 UTC
[GitHub] [pulsar] flowchartsman opened a new issue #8929: pulsar standalone docker image should support initialization of some kind
flowchartsman opened a new issue #8929:
URL: https://github.com/apache/pulsar/issues/8929
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?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] flowchartsman commented on issue #8929: pulsar standalone docker image should support initialization of some kind
Posted by GitBox <gi...@apache.org>.
flowchartsman commented on issue #8929:
URL: https://github.com/apache/pulsar/issues/8929#issuecomment-743482306
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
```
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] flowchartsman edited a comment on issue #8929: pulsar standalone docker image should support initialization of some kind
Posted by GitBox <gi...@apache.org>.
flowchartsman edited a comment on issue #8929:
URL: https://github.com/apache/pulsar/issues/8929#issuecomment-743482306
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
```
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org