Queue arguments are not re-concealed - Githubissues

rabbitmq / messaging-topology-operator

RabbitMQ messaging topology operator

Mozilla Public License 2.0

125 stars 66 forks source link

Queue arguments are not re-concealed #822

Closed kamikaze closed 3 months ago

kamikaze commented 3 months ago

Describe the bug

Queue arguments are not being re-concealed after initial values are set.

To Reproduce

Steps to reproduce the behavior:

define x-message-ttl to let's say 30000
apply
change x-message-ttl to 60000
change is not being applied

apiVersion: rabbitmq.com/v1beta1
kind: Queue
metadata:
  name: jobs-delayed
  namespace: test
spec:
  name: "jobs_delayed"
  vhost: test
  type: quorum
  arguments:
    x-message-ttl: 60000
    x-dead-letter-exchange: "xchg_jobs"
    x-dead-letter-routing-key: "job"
  autoDelete: false
  durable: true
  rabbitmqClusterReference:
    name: rabbitmq

Expected behavior x-message-ttl set to 60000

Version and environment information

Messaging Topology Operator: bitnami/rmq-messaging-topology-operator:1.14.1-debian-12-r1
RabbitMQ: bitnami/rabbitmq:3.13.2-debian-12-r4
RabbitMQ Cluster Operator: bitnami/rabbitmq-cluster-operator:2.9.0-debian-12-r1
Kubernetes: v1.29.4+k3s1

Zerpet commented 3 months ago

This is expected behaviour. Queue arguments can't be changed in RabbitMQ after declaration. We have to update the webhook to forbid updates in queue arguments.