-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
azurerm_app_configuration_key bad request after moving to 3.36.0 #19711
Comments
Git the same error after moving from 3.33.0 to 3.36.0 |
Hi @krukowskid and @arkiaconsulting , sorry for introduced this bug, a pr (#19722) has been submitted to fix it. |
This functionality has been released in v3.37.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Is there an existing issue for this?
Community Note
Terraform Version
1.3.5
AzureRM Provider Version
3.36.0
Affected Resource(s)/Data Source(s)
azurerm_app_configuration_key
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Configuration should be retrieved during refresh in terraform plan/apply like in previous version of module
Actual Behaviour
error: while checking for key's "" existence: appconfiguration.BaseClient#GetKey
Value: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: error response cannot be parsed: {"" '\x00' '\x00'} error: EOF
Steps to Reproduce
terraform init
terraform plan
Important Factoids
federated credentials auth
References
#19470
The text was updated successfully, but these errors were encountered: