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

Azure Search Services SKU Basic Supports Partitions upto 3 in azure portal but through terraform it's not supported more than 1 #28104

Closed
1 task done
Gnana-Bharathi-K opened this issue Nov 25, 2024 · 1 comment · Fixed by #28105

Comments

@Gnana-Bharathi-K
Copy link
Contributor

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

AzureRM Provider Version

4.11.0

Affected Resource(s)/Data Source(s)

azurerm_search_service

Terraform Configuration Files

resource "azurerm_search_service" "search_service" {
  name                                     = "example"
  resource_group_name                      = "example-rg-name"
  location                                 = "eastus"
  sku                                      = "basic"
  public_network_access_enabled            = false
  authentication_failure_mode              = "http403"
  local_authentication_enabled             = true
  customer_managed_key_enforcement_enabled = false
  replica_count                            = 3
  partition_count                          = 3
}

Debug Output/Panic Output

╷
│ Error: 'partition_count' values greater than 1 cannot be set for the "basic" SKU, got 3)
│
│   with module.search_service.azurerm_search_service.search_service,
│   on module\search-services.tf line 1, in resource "azurerm_search_service" "search_service":
│    1: resource "azurerm_search_service" "search_service" {
│
╵

Expected Behaviour

With provided configurations of Basic SKU and Partitions more than 1 the terraform apply should deploy with result message as

Creation complete after [id="/subscriptions//resourceGroups//providers/Microsoft.Search/searchServices/"]

Actual Behaviour


│ Error: 'partition_count' values greater than 1 cannot be set for the "basic" SKU, got 3)

│ with module.search_service.azurerm_search_service.search_service,
│ on module\search-services.tf line 1, in resource "azurerm_search_service" "search_service":
│ 1: resource "azurerm_search_service" "search_service" {

Steps to Reproduce

  1. create a search service resource with basic sku and partition count greater than 1
    resource "azurerm_search_service" "search_service" {
    name = "example"
    resource_group_name = "example-rg-name"
    location = "eastus"
    sku = "basic"
    public_network_access_enabled = false
    authentication_failure_mode = "http403"
    local_authentication_enabled = true
    customer_managed_key_enforcement_enabled = false
    replica_count = 3
    partition_count = 3
    }

  2. run terraform apply -auto-approve to reproduce the issue

Important Factoids

No response

References

The Official Microsoft Documents for reference https://learn.microsoft.com/en-us/azure/search/search-sku-tier
Which supports 9 search units and 3 counts for both partitions and replicas under SKU basic

Copy link

github-actions bot commented Jan 4, 2025

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 4, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
1 participant