fix(azurerm_log_analytics_workspace_table): Parse subscriptionId from workspaceId

[xescab]

Subscription ID used to manage tables should be the same as the Log Analytics Workspace.

Fixes #27564

Community Note

• Please vote on this PR by adding a 👍 reaction to the original PR to help the community and maintainers prioritize for review
• Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for PR followers and do not help prioritize for review

Description

Resource group for the Log Analytics Workspace should be looked at in correct subscription, as the subscription ID
is present in workspace_id variable, and the table retention should be updated correctly.

When the Log Analytics Workspace has been created previously in another subscription, the Terraform code fails, as explained in #27564.

module.diagnostic_settings.azurerm_monitor_diagnostic_setting.diag[0]: Creation complete after 14s [id=/subscriptions/xxxx-xxxx-x7aa/resourceGroups/rg-test-7fc24b/providers/Microsoft.KeyVault/vaults/kv-test-7fc24b|diag-test-7fc24b]
╷
│ Error: failed to update table Usage in workspace log-test-7fc24b in resource group rg-test-csz-7fc24b: performing CreateOrUpdate: unexpected status 404 (404 Not Found) with error: ResourceGroupNotFound: Resource group 'rg-test-csz-7fc24b' could not be found.
│
│   with module.diagnostic_settings.azurerm_log_analytics_workspace_table.table["Usage"],
│   on ../../main.tf line 37, in resource "azurerm_log_analytics_workspace_table" "table":
│   37: resource "azurerm_log_analytics_workspace_table" "table" {
│
│ failed to update table Usage in workspace log-test-7fc24b in resource group rg-test-csz-7fc24b: performing CreateOrUpdate: unexpected status 404 (404 Not Found) with error: ResourceGroupNotFound: Resource group 'rg-test-csz-7fc24b' could not be found.

PR Checklist

• I have followed the guidelines in our Contributing Documentation.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.
• I have checked if my changes close any open issues. If so please include appropriate closing keywords below.
• I have updated/added Documentation as required written in a helpful and kind way to assist users that may be unfamiliar with the resource / data source.
• I have used a meaningful PR title to help maintainers and other users understand this change and help prevent duplicate work.
  For example: “resource_name_here - description of change e.g. adding property new_property_name_here”

Changes to existing Resource / Data Source

• I have added an explanation of what my changes do and why I'd like you to include them (This may be covered by linking to an issue above, but may benefit from additional explanation).
• I have written new tests for my resource or datasource changes & updated any relevent documentation.
• I have successfully run tests with my changes locally. If not, please provide details on testing challenges that prevented you running the tests.
• (For changes that include a state migration only). I have manually tested the migration path between relevant versions of the provider.

Testing

• My submission includes Test coverage as described in the Contribution Guide and the tests pass. (if this is not possible for any reason, please include details of why you did or could not add test coverage)

Change Log

Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.

• azurerm_log_analytics_workspace_table - Correctly parse subscriptionId from workspaceId [azurerm_log_analytics_workspace_table looks for resource group in wrong subscription #27564]

This is a (please select all that apply):

• Bug Fix
• New Feature (ie adding a service, resource, or data source)
• Enhancement
• Breaking Change

Related Issue(s)

Fixes #27564

Note

If this PR changes meaningfully during the course of review please update the title and description as required.

[katbyte]

Thanks @xescab - LGTM ⛈️

[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.