[ ] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated
[ ] PR title is ready for changelog and subsystem label(s) applied
To try and standardise the messaging to the controller, implement 1 single queue that uses a new type LagoonEvent that has
EventType
lagoon:build
lagoon:task
lagoon:removal
lagoon:misc
Payload
payload will be the message that would normally be sent via the queue.
The single queue is enabled by default, and will still start the existing 4 queues for the time being. This allows the controller to be rolled out over time supporting the new single queue option, and then a Lagoon-core update will be released that changes to the single queue option by default.
A clean up script to remove the old queues will be provided with the lagoon-core release when it happens.
Checklist
To try and standardise the messaging to the controller, implement 1 single queue that uses a new type
LagoonEventthat haslagoon:buildlagoon:tasklagoon:removallagoon:miscThe single queue is enabled by default, and will still start the existing 4 queues for the time being. This allows the controller to be rolled out over time supporting the new single queue option, and then a Lagoon-core update will be released that changes to the single queue option by default.
A clean up script to remove the old queues will be provided with the lagoon-core release when it happens.
Closing issues
closes #138