Skip to content

Add support for advanced config #219

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ChunyiLyu opened this issue Jul 22, 2020 · 0 comments · Fixed by #221
Closed

Add support for advanced config #219

ChunyiLyu opened this issue Jul 22, 2020 · 0 comments · Fixed by #221
Assignees
Labels
enhancement New feature or request

Comments

@ChunyiLyu
Copy link
Contributor

ChunyiLyu commented Jul 22, 2020

Is your feature request related to a problem? Please describe.
Add support for advanced.config.

Location of advanced config is configurable through environment variable RABBITMQ_ADVANCED_CONFIG_FILE=/path/to/a/custom/location/advanced.config. By default, it is at /etc/rabbitmq/ same as rabbitmq.conf

Describe the solution you'd like

spec:
  rabbitmq:
    advancedConfig: |
    # content of the config file    
...

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Similarly to rabbitmq.conf, advanced config might need server restart for updating.

@ChunyiLyu ChunyiLyu self-assigned this Jul 22, 2020
@ChunyiLyu ChunyiLyu added the enhancement New feature or request label Jul 24, 2020
ChunyiLyu added a commit that referenced this issue Jul 29, 2020
* Add support for advanced.config

- related to issue #219 
- configured through `spec.rabbitmq.advancedConfig` as
a string
- updating advancedConfig will trigger a sts rolling restart
bc similar to `rabbitmq.conf`, advanced config is loaded at
node start
- set maxLength for advancedConfig to 100000
ChunyiLyu added a commit that referenced this issue Aug 25, 2020
* Add support for advanced.config

- related to issue #219 
- configured through `spec.rabbitmq.advancedConfig` as
a string
- updating advancedConfig will trigger a sts rolling restart
bc similar to `rabbitmq.conf`, advanced config is loaded at
node start
- set maxLength for advancedConfig to 100000
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant