Skip to content
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

dapr pubsub.rabbitmq component not honoring deleteWhenUnused=false #3583

Open
rajbaratht opened this issue Aug 21, 2024 · 2 comments
Open

dapr pubsub.rabbitmq component not honoring deleteWhenUnused=false #3583

rajbaratht opened this issue Aug 21, 2024 · 2 comments
Labels
kind/bug Something isn't working

Comments

@rajbaratht
Copy link

In what area(s)?

dapr pubsub.rabbitmq component with deleteWhenUnused: false is not honored when exchanges are created

kd component/pubsub
Name:         pubsub
Namespace:    backend
Labels:       app=dapr
              chart=components
Annotations:  meta.helm.sh/release-name: components
              meta.helm.sh/release-namespace: backend
API Version:  dapr.io/v1alpha1
Kind:         Component
Metadata:
  Creation Timestamp:  2023-06-24T14:30:17Z
  Generation:          2
  Resource Version:    671471219
Spec:
  Metadata:
    Name:   exchangeKind
    Value:  topic
    Name:   durable
    Value:  true
    Name:   deleteWhenUnused
    Value:  false
    Name:   connectionString
    Secret Key Ref:
      Key:   host
      Name:  rabbitmq-host-secret
    Name:    caCert
    Secret Key Ref:
      Key:   ca.crt
      Name:  xxx
  Type:      pubsub.rabbitmq
  Version:   v1
Events:      <none>

What version of Dapr?

dapr 1.14.1 with rabbitmq version 3.12.12

Expected Behavior

Rabbitmq exchanges should be created without AD feature set.

Actual Behavior

Rabbitmq exchanges created with AD flag set.
image

Steps to Reproduce the Problem

  1. Create pubsub.rabbitmq components with the values attached
  2. Check the exchanges created in the rabbitmq
@rajbaratht rajbaratht added the kind/bug Something isn't working label Aug 21, 2024
@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale label Oct 20, 2024
@dapr-bot
Copy link
Collaborator

This issue has been automatically closed because it has not had activity in the last 67 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.

@dapr-bot dapr-bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 27, 2024
@yaron2 yaron2 reopened this Oct 28, 2024
@yaron2 yaron2 transferred this issue from dapr/dapr Oct 28, 2024
@github-actions github-actions bot removed the stale label Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants