Terraform configuration from Tunnelbroker.
RabbitMQ docs: terraform resource, AWS docs.
The service is mostly copy-paste from other services
Details
Details
- Reviewers
kamil michal varun • jon - Commits
- rCOMM32c6aa104750: [terraform] Add Tunnelbroker
Created a Docker image from the stack and tested deployment on staging.
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
| services/terraform/remote/service_tunnelbroker.tf | ||
|---|---|---|
| 75 ↗ | (On Diff #31007) | This is to make plan difference nice - otherwise the whole jsonencode() block is made sensitive. We don't expose it anywhere so it's safe to do this. |
Comment Actions
Would it make sense to add apply_immediately (at least for staging)? If I understand the documentation correctly, currently if we make changes to the user (or add broker configuration) we would have to reboot rabbitmq manually?
| services/terraform/remote/service_tunnelbroker.tf | ||
|---|---|---|
| 22 ↗ | (On Diff #31007) | Kinda unrelated but it might make sense to pin the rabbitmq version in the docker-compose to match this |
| 23 ↗ | (On Diff #31007) | Could we use micro for now? |
Comment Actions
Yes, that's a good idea. We shouldn't do it for prod but for staging it's okay. I'll do this
| services/terraform/remote/service_tunnelbroker.tf | ||
|---|---|---|
| 22 ↗ | (On Diff #31007) | Good idea |
| 23 ↗ | (On Diff #31007) | Micro isn't production ready (according to this table), but we can save some $ on staging |