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

Enabling Analytical storage for CosmosDB is forcing re-creation #19630

Closed
1 task done
pacorreia opened this issue Dec 9, 2022 · 4 comments · Fixed by #19659
Closed
1 task done

Enabling Analytical storage for CosmosDB is forcing re-creation #19630

pacorreia opened this issue Dec 9, 2022 · 4 comments · Fixed by #19659

Comments

@pacorreia
Copy link

pacorreia commented Dec 9, 2022

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 "+1" or "me too" comments, 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

Terraform Version

1.3.5

AzureRM Provider Version

3.34.0

Affected Resource(s)/Data Source(s)

azurerm_comosdb_account

Terraform Configuration Files

resource "azurerm_resource_group" "example" {
  name     = "example-resource-group"
  location = "West Europe"
}


resource "azurerm_cosmosdb_account" "cosmosdb_account" {
  name                            = "mycosmos"
  location            = azurerm_resource_group.example.location
  resource_group_name = azurerm_resource_group.example.name
  offer_type                      = "Standard"
  kind                            = "GlobalDocumentDB"
  enable_multiple_write_locations = false
  analytical_storage_enabled      = true
}

Debug Output/Panic Output

Not needed

Expected Behaviour

When the account was created without analytical store, enabling it does not require to be re-created as per documentation and Azure Portal behaviour

It should just enable the Analytical store without forcing it to be recreated

Actual Behaviour

It's forcing it to be recreated

Steps to Reproduce

  1. Create a cosmosdB account with analytical store disabled ()
  2. then enable in the config files
  3. Apply
  4. Cosmosdb will be destroyed and created

Important Factoids

No response

References

No response

@sinbai
Copy link
Contributor

sinbai commented Dec 13, 2022

Hi @pacorreia, thanks for opening this issue. I have submitted PR to fix it. Could you keep track of it for more updates?

@pacorreia
Copy link
Author

Hi @pacorreia, thanks for opening this issue. I have submitted PR to fix it. Could you keep track of it for more updates?

Many thanks, forgot to mention that, once the analytical store is enabled, disabling it will require cosmosdb to be replaced.

@github-actions
Copy link

This functionality has been released in v3.36.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
Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
4 participants