Skip to content

Dialogflow CX - Cycle Issue | not fixed #23878

@josueelias9

Description

@josueelias9

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
  • Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.
  • If an issue is assigned to a user, that user is claiming responsibility for the issue.
  • Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Terraform Version & Provider Version(s)

Terraform v1.12.1
on linux_amd64

Affected Resource(s)

  • google_dialogflow_cx_agent
  • google_dialogflow_cx_flow
  • google_dialogflow_cx_page

Terraform Configuration

resource "random_pet" "test" {}

resource "google_dialogflow_cx_agent" "test" {
  default_language_code = "de"
  display_name          = "Bot-${random_pet.test.id}"
  location              = "global"
  time_zone             = "Europe/Berlin"
  supported_language_codes = ["en"]
}

resource "google_dialogflow_cx_flow" "startFlow" {
  parent = google_dialogflow_cx_agent.test.id
  display_name = "Start"

  transition_routes {
    intent = "${google_dialogflow_cx_agent.crewBot.id}/intents/00000000-0000-0000-0000-000000000000"
    target_page = google_dialogflow_cx_page.test.id
  }
}

resource "google_dialogflow_cx_page" "test" {
  parent = google_dialogflow_cx_flow.startFlow.id
  display_name = "Test"
}

Debug Output

Cycle issue because google_dialogflow_cx_page is using as parent the flow resource and the flow resource should add a transition_routes to the page.

Expected Behavior

Connect the resources without any problem.

Actual Behavior

How did you solve this problem? Unfortunately, there is no possibility to add a transition route to the flow resource afterwards. So you have to add a route to the flow resource as soon as you define it.

For me it seems as if the service cannot be completely mapped using Terraform.

Steps to reproduce

  1. terraform apply

Important Factoids

No response

References

#12022

b/436661214

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions