title: Can I use one packer builder with many provisioners and still run parallel builds?
body: <p>I have what seems to be like a valid use case for an unsupported - afaik - scenario, using <code>packer.io</code> and I'm worried I might be missing something...</p>
  
  <p>So, in packer, I can add: </p>
  
  <ul>
  <li>many <code>builders</code>, </li>
  <li>have a different <code>name</code> per builder, </li>
  <li>use the builder <code>name</code> in the <code>only</code> section of the provisioners and finally</li>
  <li>run <code>packer build -only=&lt;builder_name&gt;</code> to effectively limit my build to only the provisioners combined with the specific builder. </li>
  </ul>
  
  <p>This is all fine. </p>
  
  <p>What I am now trying to do, is use the same base image to create 3 different builds (and resulting AMIs). Obviously, I could just copy-paste the same builder config 3 times and then use 3 different provisioners, linking each to the respective builder, using the <code>only</code> parameter. </p>
  
  <p>This feels totally <strong>wasteful</strong> and <strong>very error prone</strong> though... It sounds like I should be able to use the same builder and just limit which provisioners are applied .. ?</p>
  
  <p>Is my only solution to use 3 copy-pasted builders? Is there any better solution?</p>