New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue deploying Dialogflow CX Version in europe-west2 #12880
Issue deploying Dialogflow CX Version in europe-west2 #12880
Comments
@jcanizalez Please were you able to test this with the #9809 fix? |
When I check the dialogflow console, I notice the version gets successfully created but then Terraform still flags the error about location. |
@BolajiAkerele2013 did you ever receive below error? If yes, how did you resolve it?
|
Yes, I configured the location settings on the Dialogflow CX console to europe-west2.
|
@shuyama1 please this is still pending for your review. |
@edwardmedia Create version request
Check the operation status request
|
Thanks for the ping! This is on my review list and will get to it soon! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
Terraform v0.15.5
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Version should be created in 'europe-west2'
Actual Behavior
"Error waiting to create Version: Error waiting for creating Version: error while retrieving operation: googleapi: Error 400: Please switch to 'europe-west2-dialogflow.googleapis.com' to access resources located in 'europe-west2'
Steps to Reproduce
terraform apply
Important Factoids
I'm authenticating as a Service Account to create these resources.
References
The text was updated successfully, but these errors were encountered: