Skip to content

CLI: apply and prune transport topology (queues, topics, subscriptions) #283

Open

Description

@adenhertog

With autoProvision: false, nothing creates or cleans up the transport topology. Ops teams want to apply it with a privileged role at deploy time and run the service with least privilege.

Scope

Supersedes #155.

Activity

  1. adenhertog commented on Oct 7, 2026

    @adenhertog
    ContributorAuthor

    Scope narrowed (maintainer, 2026-10-07): #333 delivered creating resources, the dry-run plan and permissions through bus provision. This issue now covers only pruning: finding and removing orphaned subscriptions and bindings, and optionally queues or topics, that the bus configuration no longer needs. It keeps a dry-run, removes nothing unless asked explicitly, and covers SQS and RabbitMQ.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestroadmapPart of the project roadmap

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions