Right now we store actions in S3 and give S3 urls for actions. Because we eventually need to support the Content-Signature header (in bug 1248671), we can't use S3 to serve the files. We have decided to store the javascript of action files in Postgres, and write a view that serves this content. This view will get cached by a CDN. Once we have content signing, we can include the signature in the response. Since signatures don't change, the response can still be heavily cached.

Commit pushed to master at https://github.com/mozilla/normandy https://github.com/mozilla/normandy/commit/a56c9267a8bff3b942240ff0a43b0868f93d051b Store implementations in the DB Fixes bug 1249050