Skip to content
This repository has been archived by the owner on Mar 29, 2023. It is now read-only.

Allow specifying defaults #4

Open
svetob opened this issue Nov 17, 2015 · 1 comment
Open

Allow specifying defaults #4

svetob opened this issue Nov 17, 2015 · 1 comment
Labels

Comments

@svetob
Copy link
Contributor

svetob commented Nov 17, 2015

To make the configuration more compact and easier to read, we should allow specifying defaults for queues, exchanges and bindings. Preferably, per vhost.

@rasjoh
Copy link

rasjoh commented Nov 17, 2015

users:
  admin:
      admin: true
      password: ADM1N

vhosts:
  bite:
      tracing: true

permissions:
  admin@bite:
      configure: .*
      write: .*
      read: .*

exchanges:
  bite:
    defaults:
      type: topic
      durable: true
      auto_delete: false
      internal: false
    com.meltwater.throttle.enrichment.social: {}
    com.meltwater.throttle.enrichment.social.deadletter: {}
    com.meltwater.enrichment.social@bite: {}

    com.meltwater.enrichment.social.deadletter: {}

queues:
  bite:
    defaults:
      durable: true
      auto_delete: false
      arguments:
        x-message-ttl: 10000
    to-throttle-enrichment-social: {}
    to-throttle-enrichment-social-deadletter: {}
    to-pipeline-social: {}
    to-pipeline-social-deadletter: {}

bindings:
  bite:
    defaults:
      destination_type: queue
      routing_key: "#"
    com.meltwater.throttle.enrichment.social@to-throttle-enrichment-social: {}
    com.meltwater.throttle.enrichment.social.deadletter@to-throttle-enrichment-social-deadletter: {}
    com.meltwater.enrichment.social@to-pipeline-social: {}
    com.meltwater.enrichment.social.deadletter@to-pipeline-social-deadletter: {}

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants