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

[💡 FEATURE REQUEST]: add support for multiple broker connections #1962

Open
shieldz80 opened this issue Jul 3, 2024 · 1 comment
Open
Assignees
Labels
C-feature-request Category: feature requested, but need to be discussed

Comments

@shieldz80
Copy link

Plugin

JOBS

I have an idea!

Hi,

Million thanks for the awesome project!

In my projects at work, I need to connect to different brokers in certain scenarios. For example I need to consume messages from one broker that is assigned to my team, and then during the processing of messages I need to push messages to another broker that is assigned to another team.

I was wondering if perhaps something like this would make sense (using amqp as an example):

amqp:
    # connection name
    brokerA:
        addr: amqp://guest:guest@brokerA:5672/
        tls:
            key: ""
            cert: ""
            root_ca: ""
            client_auth_type: no_client_certs
    # connection name
    brokerB:
        addr: amqp://guest:guest@brokerB:5672/
        tls:
            key: ""
            cert: ""
            root_ca: ""
            client_auth_type: no_client_certs
            
jobs:
    pipelines:
        pipeline-1:
            driver: amqp
            config:
                # this would be a new option
                connection: brokerA
        pipeline-2:
            driver: amqp
            config:
                # this would be a new option
                connection: brokerB
@shieldz80 shieldz80 added the C-feature-request Category: feature requested, but need to be discussed label Jul 3, 2024
@rustatian
Copy link
Member

Hey @shieldz80 👋
Thank you for the feature request 👍
Generally, I agree with that improvement, but let us see the community reactions.

@rustatian rustatian moved this to 📋 Backlog in Jira 😄 Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature-request Category: feature requested, but need to be discussed
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants