We should do whatever puppet monkeying we need to get striker running on Labtest. I suspect this will prove useful in the long run, and it's always nice to test our production-ish deployment process on labtest after a merge.
|operations/puppet||production||+3 -0||labweb oauth: use labtestwikitech, not prod wikitech|
The big trick here will be figuring out how to separate from scap3 for the deploy step. The existing Puppet setup uses service::uwsgi which automatically sets up scap3 deployment. It looks like that can be turned off by passing deployment => 'anything_but_scap3' to the service::uwsgi define. Its a bit hacky but it should work. Doing that would likely mean converting the Puppet config to the newly defined profiles and roles layout and introducing more hiera config that could be overloaded in a role::striker::web_test class.