Alex_B_Wilson's post is very much on point. This is available right now in nearly all field versions of gateway.
In 9.1 and later, we ship a dockerized gateway, and one of the premier ways of implementing a devOps story ends up starting with containerization, so that's a big start.
DevOps is about reducing dependencies. The Dockerized gateway and command line stye deployment lets you build on demand. This begins to develop a toolchain that fits in the DevOps mindset. As Alex mentions, we're already fully API addressable for configuration push so we can be configured from scratch entirely via APIs and scripting.
Finally, the majority of devOps efforts are all about reducing effort and errors. Scripting is crucial, as is repeatability. If we look at the way tooling is built from the devOps perspective, the development lifecycle needs to be supported - so Alex_B_Wilson's example here can be used to move between dev, QA, and production.
This also implies the artifacts - the policy exports - can be checked into a version control system of your choice and can be used in CI/CD - check out from version control system, build, push, etc.