title: Same CloudFormation template to parameterize DeletionPolicy?
body: <p>As a DevOps guy I wanted to use the same template to provision both Dev and Prod stacks... Where dev stacks should not have any <code>DeletionPolicy</code> but Prod stacks should utilize a <code>DeletionPolicy</code></p>
  
  <p>So, at first sight CFT gives an ok tooling for this but.... there is no possibility to parametrize S3 <code>DeletionPolicy</code> (that I've been able to locate at least)...</p>
  
  <p>Here's some threads I dug up</p>
  
  <ul>
  <li><a href="https://forums.aws.amazon.com/message.jspa?messageID=560586" rel="nofollow noreferrer">https://forums.aws.amazon.com/message.jspa?messageID=560586</a></li>
  <li><a href="https://www.unixdaemon.net/cloud/cloudformation-annoyance-deletion-policy-parameters/" rel="nofollow noreferrer">https://www.unixdaemon.net/cloud/cloudformation-annoyance-deletion-policy-parameters/</a></li>
  </ul>
  
  <p>The <em>suggested workaround</em> from AWS was to make the whole resource conditional, which leads us duplicating the resource and create a <code>„Deletable</code> and <code>„Undeletable</code> versions of it and all the depending resources should handle that condition... </p>
  
  <p>This seems wonky and bloated, is there a way to parameterize this or a better methodology to accomplish my end goal?</p>