
CraigL.22163 (Customer) asked a question.
It appears to me that the only way to put our workflows under source control is to export them, and manually make those updates. It also appears that the deployment model is to export the workflow or folders from oktapreview.com, then import them into okta.com.
I am looking to include workflows into a CI/CD process, and need an automated way to tie into source control (GitHub), and a CD process (Azure Pipeline). Any ideas?

Craig,
Versioning control and an API to manage flows is on the roadmap but isn't here yet (The details of what that looks like is unknown to me).
Currently, you are correct. The only method to "version control" would be manual naming, and exporting/importing flows/flowpacks from one location to another. There is currently no automated process to accomplish this.
Thanks for the response.