Genesys Cloud - Developer Community!

 View Only

Sign Up

  • 1.  Managing state, credentials, and other suggested 'Best Practices'

    Posted 10 hours ago
    1. We have already built and managed many objects in our Genesys environments through the UI prior to starting our CX as Code journey. We're now attempting to implement CX as Code for creating, updating, and deleting all objects moving forwards. To date, our initial proof of concepts have focused solely on creating new objects in our organizations. We now want to want to import/include all of the objects in our environments (even the objects that were created prior to CX as Code) into our state files. We did not find any resources on the CX as Code best practices site. In short, is there a documented process for importing all objects into CX as Code practices that your or your team can point us towards?
    2. Do you have other customers that manage Flow objects with CX as Code? If so, are they just building them out in the UI, then importing their configurations into their CX as Code solution?

    3. On a similar note, do other customers manage Oauth/Integration credentials via CX as Code? If so, how are they dealing with the secret/credentials with respect to CX as Code?

    #CXasCode

    ------------------------------
    Steve Hentz
    Technical Account Manager
    ------------------------------


  • 2.  RE: Managing state, credentials, and other suggested 'Best Practices'

    Posted 8 hours ago
    Edited by Lucas Woodward 8 hours ago
    Hey Steve,
     
    I wrote an article about CX as Code, including exporting existing resources which may be useful?
     
     
    The relevant sections to your questions are:

    To answer each of your questions, based on my experience:

    Is there a documented process for importing all objects into CX as Code practices that your or your team can point us towards?

    The Genesys Cloud Dev Blog has a useful article Introducing Genesys Cloud TF export in CX as Code that explains the export capabilities offered by CX as Code, namely:
     

    I suspect the latter (tf_export) is what you're after as it can export resources based on a pattern.

    Do you have other customers that manage Flow objects with CX as Code?

    We manage flows via CX as Code. If we're making substantial changes to the flow then we have to export them to YAML (via the UI) and add in the substitutions before committing to our source control. However the simpler changes can be made directly to the YAML files.

    We have automated tests for most flows so we can catch any issues in making the changes directly.

    Do other customers manage Oauth/Integration credentials via CX as Code?

    We have a OAuth Client that is created manually for CX as Code, which has the relevant permissions to manage other OAuth Clients.

    Hopefully this answers your questions. I'm happy to expand on topics if not. 

    ------------------------------
    Lucas Woodward
    Winner of Orchestrator of the Year, Developer (2025)

    LinkedIn - https://www.linkedin.com/in/lucas-woodward-the-dev
    Newsletter - https://makingchatbots.com
    ------------------------------

    Original Message


Related Content