Azure / Azure/azure-rest-api-specs

[BUG] Missing Enterprise_E200 sku for RedisEnterprise

Open
#31,589 1 comment 0 reactions 1 assignee View on GitHub

@revanthballa1188 is already working on this.

Since Nov 19, 2024.

bug customer-reported Mgmt question
Dominant language
TypeSpec
Stars
3.1k
Forks
6k
Avg merge
2d 22h
Merged PRs (30d)
444

Description

### API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/2afa5b356adf6cf51209d2cf28d38644c69d9832/specification/redisenterprise/resource-manager/Microsoft.Cache/preview/2024-06-01-preview/redisenterprise.json

### API Spec version

2024-06-01-preview

### Describe the bug

`2024-06-01-preview` is missing `Enterprise_E200` sku which was supported in `2023-10-01-preview`

2023-10-01-preview: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/redisenterprise/resource-manager/Microsoft.Cache/preview/2023-10-01-preview/redisenterprise.json

2024-06-01-preview: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/redisenterprise/resource-manager/Microsoft.Cache/preview/2024-06-01-preview/redisenterprise.json#L1406-L1414

### Expected behavior

`Enterprise_E200` to be supported in all version post `2023-10-01-preview`

### Actual behavior

`Enterprise_E200` is not support and our terraform pipeline is now failing with

```
Error: expected "sku_name" "name" segment to be one of ["Enterprise_E5", "Enterprise_E50", "Enterprise_E1", "Enterprise_E100", "Enterprise_E10", "Enterprise_E20", "EnterpriseFlash_F1500", "EnterpriseFlash_F700" or "EnterpriseFlash_F300"], got "Enterprise_E200-10"

│ with module.database.module.rediscluster["xxxx"].azurerm_redis_enterprise_cluster.redis_cluster,
│ on .terraform/modules/database/modules/azure-redis-enterprise/main.tf line 14, in resource "azurerm_redis_enterprise_cluster" "redis_cluster":
```

after upgrading to use `hashicorp/azurerm` version 4.0+

### Reproduction Steps

Use terraform `hashicorp/azurerm` version 4.0+ to provision redis enterprise in azure with E200 sku

### Environment

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.