You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #508, RabbitMQ maintainers agreed to support a small number of environment variables that would make node seeding convenient in certain environments (such as ECS or service containers used by GitHub, GitLab and so on). This should ship in 3.9.4rabbitmq/rabbitmq-server#3299.
However, since the entrypoint of this image now (#467) black lists most previously supported env variables. We should whitelist
the four agreed on in #508 so that they are allowed and propagated to RabbitMQ nodes.
That should make it easier to use this image in more environments without introducing any entrypoint complexity (or undoing any important changes from #467).
michaelklishin
changed the title
Whitelist a small number of env variables used to seed RabbitMQ nodes
Whitelist a small number of env variables used to seed essential node data (new in RabbitMQ 3.9.4)
Aug 11, 2021
In #508, RabbitMQ maintainers agreed to support a small number of environment variables that would make node seeding convenient in certain environments (such as ECS or service containers used by GitHub, GitLab and so on). This should ship in
3.9.4
rabbitmq/rabbitmq-server#3299.However, since the entrypoint of this image now (#467) black lists most previously supported env variables. We should whitelist
the four agreed on in #508 so that they are allowed and propagated to RabbitMQ nodes.
That should make it easier to use this image in more environments without introducing any entrypoint complexity (or undoing any important changes from #467).
@tianon @yosifkit does this sound reasonable to you?
The text was updated successfully, but these errors were encountered: