FAQs
(https://developer.genesys.cloud/api/rest/CX-as-Code/#faqs)
Is there any additional cost or is this capability fully covered under the Genesys Cloud 3 licenses?
No additional cost. It is open source and uses our public APIs.
Currently there is support for the People, Permission and the Contact Center ACD objects. How does the roadmap look especially for more complex objects like scripts and architect flows?
For now we are prioritizing object types based on customer feedback and plan to continue to add more over time.
How to get started with existing already configured orgs? Is it the best way to export your production org objects and then start applying them on each org to make sure the environments are consistent and then use the exported files as baseline under source control and update them and apply through the path to production in your pipelines?
Exports from one org can be applied to another org, but Terraform always attempts to create resources on the initial apply. It will not perform a "create or update" operation, which means resources with the same identifier that already exist will fail to create. Because of this, it works best if the org where you import a config file is a brand new org.
How does it support audit trail? Only through source control system audit trail?
The plugin itself does not create an audit trail. This must be done by the user, most likely with source control of the Terraform files.
How does it support environment comparison? Export the configuration in two orgs and then use some text file comparison tool to highlight differences?
There is no comparison support today. Exports from different orgs can vary in resource order and naming, so a raw text comparison will likely be incorrect.
Is CX as Code well-suited for making one-time/infrequent bulk operations?
CX as Code is more of a way to manage your GC configuration as a whole for the lifetime of your org. We recommend using the CLI to make infrequent, bulk changes.
Are there any limits on the number of config objects that CX as Code will support?
We are not aware of any hard limits on the size of the Terraform config file.
Can I use CX as Code for UI development?
The CX as Code project is a Terraform provider that wraps Genesys Cloud APIs (very similar to how CloudFormation wraps AWS APIs). The configuration is defined in a text file and creates/updates/deletes are processed by the Terraform CLI locally or by one of Terraform’s hosted offerings. This is not something that would be used by the Genesys Cloud UI.
Is CX as Code subject to rate limiting?
The provider may run into public API rate limiting if there are a large number of updates, but it will retry with backoff.
Can I contribute to CX as Code?
CX as Code is open-source. You are welcome to open a pull request in the repo.
CX as Code is provided by Terraform. Will Genesys run Terraform for my org?
Terraform requires customers to create an account with Terraform.cloud or to run the CLI in their own infrastructure.
Will I be able to see the changes made with CX as Code?
Yes. Changelogs will be generated automatically on release. Additionally, actions that are supported in our Audits API will include changes made using CX as Code.