-
Notifications
You must be signed in to change notification settings - Fork 42
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
[MM-61281] allow customizable public ip allocation #868
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to me!
(I'm ever so slightly concerned that there will come a time when we have a config knob for each single Terraform field 😂)
Yeah... what I would like is to group configuration by server type, instead of having that much of root level attributes. Should be easier to navigate, but is a big change at the moment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Man, this is becoming a maze of config options :P
Can we update deployer.sample.json and deployer.sample.toml?
Do we also need to update examples/ci/deployer.json every time we add a new field in deployer config @agarciamontoro ?
Oh boy I keep forgetting something. I thought I got it right this time 🙃 |
I have an item in the load-test tool release playbook to update it just before the release, no need to be on top of this every time. |
Summary
Right now the terraform code forces public ip address on agents and proxy servers by default, adding a new configuration option to allow disabling that configuration attribute in the terraform configuration.
Ticket Link
https://mattermost.atlassian.net/browse/MM-61281