Skip to content
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_monitor_private_link_scope produces inconsistent result after apply #28356

Open
1 task done
q-renjoseph opened this issue Dec 20, 2024 · 1 comment
Open
1 task done

Comments

@q-renjoseph
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Terraform Version

1.9.0

AzureRM Provider Version

3.117.0

Affected Resource(s)/Data Source(s)

azurerm_monitor_private_link_scope

Terraform Configuration Files

resource "azurerm_monitor_private_link_scope" "ampls" {
  name                  = var.name
  resource_group_name   = var.resource_group_name
  ingestion_access_mode = "PrivateOnly"
  query_access_mode     = "PrivateOnly"
}

Debug Output/Panic Output

│ Error: Provider produced inconsistent result after apply


│ When applying changes to
│ module.azure_monitor_private_link_scope.azurerm_monitor_private_link_scope.ampls,
│ provider "provider[\"registry.terraform.io/hashicorp/azurerm\"]" produced
│ an unexpected new value: Root object was present, but now absent.
│ 
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.

Expected Behaviour

No response

Actual Behaviour

No response

Steps to Reproduce

No response

Important Factoids

No response

References

No response

@teowa
Copy link
Contributor

teowa commented Dec 23, 2024

Hi @q-renjoseph, thanks for submitting this!
I cannot reproduce this in my local environment, this might be caused by unstable API. Could you please try it again with debug option and check the API flow if Azure API is returning unexpected 404 status code in GET operation after PUT.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants