Genesys Cloud - Developer Community

Hi Edward

sdk_debug = true is a provider level argument. This gives me the log book for all the API calls.

provider "genesyscloud" {
     oauthclient_id     = "xxxx"
     oauthclient_secret = "xxxxx"
    aws_region         = "us-east-1"
    sdk_debug          = true
}

Hi Venkata.

When add the sdk = true in main.ft file is present the error:

 terraform apply
╷
│ Error: Unsupported argument
│
│   on main.tf line 28, in resource "genesyscloud_tf_export" "export":
│   28:   sdk_debug          = true
│
│ An argument named "sdk_debug" is not expected here.

I get not the option and execute the terraform apply, but enable_dependency_resolution = true without use_legacy_architect_flow_exporter in the main.tf file, when ececute "terraform apply", for default, use_legacy_architect_flow_exporter is set to true as follow and execution it starts without end or lasts for hours:

 terraform apply

Terraform used the selected providers to generate the following execution plan. Resource actions are
indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # genesyscloud_tf_export.export will be created
  + resource "genesyscloud_tf_export" "export" {
      + compress                           = false
      + directory                          = "./export"
      + enable_dependency_resolution       = true
      + export_as_hcl                      = false
      + export_computed                    = true
      + export_format                      = "hcl"
      + id                                 = (known after apply)
      + ignore_cyclic_deps                 = true
      + include_filter_resources           = [
          + "genesyscloud_flow::Menu_Pruebas_Edward",
        ]
      + include_state_file                 = true
      + log_permission_errors              = true
      + split_files_by_resource            = false
      + use_legacy_architect_flow_exporter = true
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

_____________________________________

For export only flow architect with dependency (data actions, queues, data table, etc) how should I place of options and filter?

Best regards, Edward.

Hi @EdwardEnriqueHerrera,

Thanks for your question! Let me clarify a couple of points for you:

1. Cx as Code Resource Support: You're on the right track with using the export resource for migration. Cx as Code supports most resources, and you can find the full list of supported ones in the resources section of the documentation here: Genesys Cloud Terraform Provider. This should help you confirm exactly what's covered.
2. Using enable_dependency_resolution: This setting is useful when you want to export specific resource types along with their dependencies. For example, if you're only exporting genesyscloud_flow and its related dependencies, enabling this option ensures those dependencies are included. However, if your goal is to export the entire organization, you don’t need to enable enable_dependency_resolution. Doing so could lead to duplicate or cyclical dependencies, as the export process will traverse the entire dependency tree by default. If you’re still running into issues  (long running too) where certain resources aren’t exporting completely, I’d recommend opening a Care ticket with Genesys. Be sure to include the relevant logs, and the backend team can dig into the root cause for you.
   
   Please include 

   sdk_debug          = true

   in provider definition.
   
   

   and add TF_LOG=DEBUG when doing terraform apply

Hope this clears things up! Let me know if you have any other questions.

Thanks