I'm trying to piece together a general strategy for replpicating environments. I know Terraform can be used for some of this, but I'm struggling on a few bits.
- The CX as Code documentation presumes the author is editing files locally and pushing to Terraform, either directly, or vis a source control automation. How can we tell Terraform to look at the as-built configuration of one Genesys org, rather than a bunch of text files? My concdern is users skipping the file part of this, because typical GCCX admins aren't writing code, they are clicking things.
- How are dependencies handled? Example, an architect flow has dependencies on prompts, common modules, data actions, bot flows, other flows, etc. Those need to be replicated as well or a publish would fail.
The only documentation I could find is a blueprint for deploying a single, extremely basic Architect flow. That is not a real-world use case, as Architect Flow authors are not writing flows in YAML for anything even remotely complex, they are using Architect. I also couldn't find documentation on using Archy to pull flows out of Genesys, only to push TO Genesys. The former might be how we'd feed a whole inventory of flows to Terraform on a schedule (since flow publish events are limited to AWS Event Bridge, which we can't easily use).
#CXasCode------------------------------
Paul McGurn
Senior Manager, Telecom & DevOps
Persistent Systems
------------------------------