Basutkar_Avinash | 2024-08-13 09:54:58 UTC | #1
When we have new Dev flows fully tested & ready to push to Prod, we usually "Save As" the flow in Prod environment and then update the dependencies in the new Prod flow to prod version of data actions/tables.
Also, say there are changes done to existing to Dev flow and they are tested, we then go & add the same changes in existing Prod version of that flow.
Is this ideal approach? Or is there better & safe way to push to Prod?
John_Carnell | 2024-08-13 18:40:11 UTC | #2
Hi Basutkar,
There is no single one-size-fits-all answer. The most common way to do this is to our Archy tool to export the flows and then use a CI/CD pipeline using our CX as Code Terraform provider to deploy the architect flow and any of its dependent objects. Some of our larger customers also use the CX as Code export capabilities and/or the professional services team's BCP/DR application to synchronize code between their product environments. I suggest you checkout:
- Development Center CX as Code Information
- Terraform CX as Code Registry
- Our Genesys Cloud Blueprints repo, particularly our CX as Code example using GitHub Actions
I hope that helps.
Thanks, John Carnell Director, Developer Engagement
Basutkar_Avinash | 2024-08-15 11:00:31 UTC | #3
Thank you, John. I will refer the documentation you've shared.
system | 2024-09-15 11:01:31 UTC | #4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 27849