-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Support for number_of_workers in app_service #10143
Support for number_of_workers in app_service #10143
Conversation
@jackofallops - are you able to take a look at this one for me? I've added tests (both resource and unit tests) and updated the docs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the pr @AdamCoulterOz - but this has caused a bunch of test to fail:
------- Stdout: -------
=== RUN TestAccAppServiceSlot_authSettingsTokenRefreshExtensionHours
=== PAUSE TestAccAppServiceSlot_authSettingsTokenRefreshExtensionHours
=== CONT TestAccAppServiceSlot_authSettingsTokenRefreshExtensionHours
testing.go:684: Step 0 error: errors during apply:
Error: Error updating Configuration for App Service Slot "acctestRG-210113192134430089"/"acctestASSlot-210113192134430089": web.AppsClient#CreateOrUpdateConfigurationSlot: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="Number of Web workers must be greater than zero." Details=[{"Message":"Number of Web workers must be greater than zero."},{"Code":"BadRequest"},{"ErrorEntity":{"Code":"BadRequest","ExtendedCode":"04004","Message":"Number of Web workers must be greater than zero.","MessageTemplate":"Number of Web workers must be greater than zero.","Parameters":[]}}]
on /opt/teamcity-agent/temp/buildTmp/tf-test826555480/main.tf line 31:
(source code not available)
--- FAIL: TestAccAppServiceSlot_authSettingsTokenRefreshExtensionHours (205.30s)
FAIL
Thanks @katbyte - here is my local test results: The new acctest for this new optional attribute:
Reproducing the acctest that failed on your side:
I also ran the same failed acctest on master and it passed fine. Can you provide some direction on why an optional field may have broken a different test (which I assume couldn't have referenced that field)? I probably need to set a sane default for it then? But it's not always applicable, and Was there any other acctests that failed? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @AdamCoulterOz
Thanks for this, and apologies for the delay in getting to review. I've left a couple comments below that I believe should help resolve the testing issue highlighted, otherwise looks to be fine. I'll loop back after I finish a few other things to check in.
Co-authored-by: Steve <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @AdamCoulterOz - this LGTM 👍
This has been released in version 2.45.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.45.0"
}
# ... other configuration ... |
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. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Fixes #8555