<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Maybe I don’t really understand this that well. <div class=""><br class=""></div><div class="">I thought the issue has always been that </div><div class=""><br class=""></div><div class="">1. We have other scripts/deployment methods that rely on the deployment-template: <a href="https://github.com/openshift/ansible-service-broker/blob/master/templates/deploy-ansible-service-broker.template.yaml" class="">https://github.com/openshift/ansible-service-broker/blob/master/templates/deploy-ansible-service-broker.template.yaml</a></div><div class="">2. this means when you update that template and change something the script is expecting/not expecting to do then a bunch of people have issues deploying the broker.</div><div class=""><br class=""></div><div class="">What I was hoping is that it should be assumed that if you create a script and point to the master branch of the deployment template that this will change and we will not make changes to the deployment template to support that script. </div><div class="">then we should have deployment-templates for either each sprint, git commit tagged, that set a specific broker image based on the sprint tag that people who want to know their script will always work in the similar way. This deployment template should also use the sprint tag for the APBs so we now that will also work. This is what the run_latest_build.sh should point to IMO. Catasb appears to already have the ability to determine with template you want to use, so we should just make sure that this is documented and we can default to master branch deployment template. </div><div class=""><br class=""></div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 14, 2018, at 3:27 PM, Erik Nelson <<a href="mailto:ernelson@redhat.com" class="">ernelson@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" class="">1. Tag every deployment template to use a specific version of the broker.<br class=""></blockquote><br class="">Do we have an official support list? I'm concerned with one and only<br class="">template, and I don't think we should be supporting much else:<br class=""><br class=""></div></div></blockquote>I am confused by official support list sorry, can you explain more?</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class=""><a href="https://github.com/openshift/ansible-service-broker/blob/master/templates/deploy-ansible-service-broker.template.yaml" class="">https://github.com/openshift/ansible-service-broker/blob/master/templates/deploy-ansible-service-broker.template.yaml</a><br class=""><br class=""><blockquote type="cite" class="">4. Need help to understand what mini shift should do, @erik would the combination of branch and image tag be enough?<br class=""></blockquote><br class="">I have the minishift addon to pull this from github, pegged to a tag.<br class="">It's hard set to our latest release, and requires manual updates.<br class="">It's an explicit desire to have this pegged, but easy to update as we move.<br class=""></div></div></blockquote></div></div><div class="">So minishift already behaves as I have described above except the deployment template that it points to does not specify a specific version of the broker and APBs to use? </div><div class=""><br class=""></div></body></html>