title: How To Configure Queue Name for Queue Trigger In Azure Function App
body: <p>I'm creating a function app in Azure and want to use a queue trigger.
  I know how to configure the queue name at design time, e.g:</p>
  
  <p><div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
  <div class="snippet-code">
  <pre class="snippet-code-html lang-html prettyprint-override"><code>[FunctionName("MyTestFunction")]
  public static void Run([QueueTrigger("myqueue-items", Connection = "testdelete")]string myQueueItem, TraceWriter log)</code></pre>
  </div>
  </div>
  </p>
  
  <p>However, I'd like to be able to define and reference it in a configuration file.
  I'm aware of the existence of function.json (Probably this one), host.json and local.settings.json, but I don't know how to set a queue name in there and have it be referenced in the function.</p>
  
  <p>If I deploy a freshly created function created in visual studio (With the new 15.3 update), I can see the following in the function.json file post deployment (even though the file doesn't exist when i develop locally):</p>
  
  <p><div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
  <div class="snippet-code">
  <pre class="snippet-code-html lang-html prettyprint-override"><code>  "bindings": [
      {
        "type": "queueTrigger",
        "queueName": "myqueue-items",
        "connection": "testdelete",
        "name": "myQueueItem"
      }</code></pre>
  </div>
  </div>
  </p>
  
  <p>I've found that if I create that file, and change the "queueName" to something that doesn't match the value in the actual function, it unfortunately doesn't override it (That would have been too easy I guess).</p>
  
  <p>How can I reference the bindings in the function.json in the functions QueueTrigger attribute?</p>
  
  <p>Presumably whatever the solution is will allow me to do the same with poison queue handling?</p>
  
  <p>The reason I want to do this, is because I need to deploy multiple instances of the exact same function, but pointing each one at a different queue (In order to get around max memory limitations).</p>
  
  <p>Thanks.</p>