# Plugin in a step to imply agent queue

**URL:** <https://forum.buildkite.community/t/plugin-in-a-step-to-imply-agent-queue/147>\
**Category:** Features Requests\
**Created:** [December 10, 2018, 8:02am UTC](https://forum.buildkite.community/t/plugin-in-a-step-to-imply-agent-queue/147 "2018-12-10T08:02:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![moensch](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/moensch/32/33_2.png) [@moensch](https://forum.buildkite.community/u/moensch)\
**Post date:** [December 10, 2018, 8:02am UTC](https://forum.buildkite.community/t/plugin-in-a-step-to-imply-agent-queue/147/1 "2018-12-10T08:02:20Z")

</div>

I can think of a couple of use cases at my company where I’d want a certain plugin to always run on a specific queue.  
It would be cool if I could somehow tie plugins to a queue. So if someone in any given build step invokes a plugin, but does not specify an agent queue for that step, during pipeline upload, that step would “magically” be tied to a given queue.

---

<div class="post-metadata">

**Author:** ![anon18197598](https://avatars.discourse-cdn.com/v4/letter/a/9d8465/32.png) [@anon18197598](https://forum.buildkite.community/u/anon18197598)\
**Post date:** [December 10, 2018, 8:42am UTC](https://forum.buildkite.community/t/plugin-in-a-step-to-imply-agent-queue/147/2 "2018-12-10T08:42:28Z")

</div>

Interesting idea! We’ve considered the idea of agent-level plugins that you’d configure via the agent configuration vs a pipeline configuration.

This can generally be accomplished with a “hooks” repo referenced from agent hooks like [https://github.com/buildkite/aws-secrets-manager-agent-hooks/blob/master/INSTALL.md](https://github.com/buildkite/aws-secrets-manager-agent-hooks/blob/master/INSTALL.md).

The issue I see with calling them “plugins” is that it gets confusing how the semantics differ.

---

<div class="post-metadata">

**Author:** ![anon46008679](https://avatars.discourse-cdn.com/v4/letter/a/da6949/32.png) [@anon46008679](https://forum.buildkite.community/u/anon46008679)\
**Post date:** [December 28, 2018, 10:55pm UTC](https://forum.buildkite.community/t/plugin-in-a-step-to-imply-agent-queue/147/3 "2018-12-28T22:55:41Z")

</div>

Another idea for you @moensch, might be to have a plugin that’s designed to be used as the pipeline upload step, and it knows how to do the pinning to a queue?

```auto
steps:
  - label: ":pipeline:
    plugins:
      - my-pipeline-upload-plugin#v1.0.0: ~

```

The plugin could define it’s own `command` hook, and do the `buildkite-agent pipeline upload` with the queue pinned as you need.