New Resource: azurerm_automation_software_update_configuration

[wuxu92]

add support for azurerm_automation_software_update_configuration

--- PASS: TestAccSoftwareUpdateConfiguration_basic (174.92s)
--- PASS: TestAccSoftwareUpdateConfiguration_update (312.09s)
PASS

[katbyte]

Have some test failures:

------- Stdout: -------
=== RUN   TestAccSoftwareUpdateConfiguration_update
=== PAUSE TestAccSoftwareUpdateConfiguration_update
=== CONT  TestAccSoftwareUpdateConfiguration_update
    testcase.go:110: Step 1/4 error: Error running apply: exit status 1
        
        Error: creating Software Update Configuration: (Name "acctest-suc-220908181914774434" / Automation Account Name "acctest-220908181914774434" / Resource Group "acctestRG-auto-220908181914774434"): automation.SoftwareUpdateConfigurationsClient#Create: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="Error - chosen Azure Automation does not have a Log Analytics workspace linked for operation to succeed. To know which regions are supported for linking, see our documentation at: https://aka.ms/Automation-Region-Mapping"
        
          with azurerm_automation_software_update_configuration.test,
          on terraform_plugin_test.tf line 42, in resource "azurerm_automation_software_update_configuration" "test":
          42: resource "azurerm_automation_software_update_configuration" "test" {
        
        creating Software Update Configuration: (Name
        "acctest-suc-220908181914774434" / Automation Account Name
        "acctest-220908181914774434" / Resource Group
        "acctestRG-auto-220908181914774434"):
        automation.SoftwareUpdateConfigurationsClient#Create: Failure responding to
        request: StatusCode=400 -- Original Error: autorest/azure: Service returned
        an error. Status=400 Code="BadRequest" Message="Error - chosen Azure
        Automation does not have a Log Analytics workspace linked for operation to
        succeed. To know which regions are supported for linking, see our
        documentation at: https://aka.ms/Automation-Region-Mapping"
--- FAIL: TestAccSoftwareUpdateConfiguration_update (123.43s)
FAIL

[wuxu92]

tests passed

[katbyte]

we have a flakey test here:

 Error: creating Software Update Configuration: (Name "acctest-suc-220913160651661230" / Automation Account Name "acctest-220913160651661230" / Resource Group "acctestRG-auto-220913160651661230"): automation.SoftwareUpdateConfigurationsClient#Create: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="Error - chosen Azure Automation does not have a Log Analytics workspace linked for operation to succeed. To know which regions are supported for linking, see our documentation at: https://aka.ms/Automation-Region-Mapping"

this might be eventually consistancy issue with LA?

[wuxu92]

The newest commit id is 43d387559f4df8c8e0abd3782adb21ed9969d4a8 which tests passed, and the commit id of failed test is a1aa73a7228320435065af934afd69827c4c42cb which is a bit confusing i did not push such a commit. so @katbyte could you please rerun this test with commit id 43d387559f4df8c8e0abd3782adb21ed9969d4a8?

[katbyte]

Still have test failures:

------- Stdout: -------
=== RUN   TestAccSoftwareUpdateConfiguration_update
=== PAUSE TestAccSoftwareUpdateConfiguration_update
=== CONT  TestAccSoftwareUpdateConfiguration_update
    testcase.go:110: Step 1/4 error: Error running apply: exit status 1
        
        Error: creating Software Update Configuration: (Name "acctest-suc-220920161519073441" / Automation Account Name "acctest-220920161519073441" / Resource Group "acctestRG-auto-220920161519073441"): automation.SoftwareUpdateConfigurationsClient#Create: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="Error - chosen Azure Automation does not have a Log Analytics workspace linked for operation to succeed. To know which regions are supported for linking, see our documentation at: https://aka.ms/Automation-Region-Mapping"
        
          with azurerm_automation_software_update_configuration.test,
          on terraform_plugin_test.tf line 36, in resource "azurerm_automation_software_update_configuration" "test":
          36: resource "azurerm_automation_software_update_configuration" "test" {
        
        creating Software Update Configuration: (Name
        "acctest-suc-220920161519073441" / Automation Account Name
        "acctest-220920161519073441" / Resource Group
        "acctestRG-auto-220920161519073441"):
        automation.SoftwareUpdateConfigurationsClient#Create: Failure responding to
        request: StatusCode=400 -- Original Error: autorest/azure: Service returned
        an error. Status=400 Code="BadRequest" Message="Error - chosen Azure
        Automation does not have a Log Analytics workspace linked for operation to
        succeed. To know which regions are supported for linking, see our
        documentation at: https://aka.ms/Automation-Region-Mapping"
--- FAIL: TestAccSoftwareUpdateConfiguration_update (98.30s)
FAIL

[wuxu92]

sorry, it was my mistake. the root cause of test failure is the region map of automation's linked log analytics workspace is mismatched. because TeamCity use east us to create log analytics workspace and automation/softwareconfigurationupdate which EastUS is mapping to EastUS2 as screenshot blow. so I choose westus (in code) for tests of this resource.

https://learn.microsoft.com/en-us/azure/automation/how-to/region-mappings

[katbyte]

Tests pass now @wuxu92 ! thanks LGTM ⚙️

[github-actions]

This functionality has been released in v3.24.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!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.