azurerm_redis_cache - output redis_primary_connection_string ssl=false but port is 6380

[Poil]

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 and review the contribution guide to help.

Terraform Version

1.5.7

AzureRM Provider Version

3.75.0

Affected Resource(s)/Data Source(s)

azurerm_redis_cache

Terraform Configuration Files

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

# NOTE: the Name used for Redis needs to be globally unique
resource "azurerm_redis_cache" "example" {
  name                = "example-cache"
  location            = azurerm_resource_group.example.location
  resource_group_name = azurerm_resource_group.example.name
  capacity            = 2
  family              = "C"
  sku_name            = "Standard"
  enable_non_ssl_port = true
  minimum_tls_version = "1.2"

  redis_configuration {
  }
}

Debug Output/Panic Output

.

Expected Behaviour

example.redis.cache.windows.net:6380,password=xxxxxxxxxxxx=,ssl=True,abortConnect=False

Actual Behaviour

example.redis.cache.windows.net:6380,password=xxxxxxxxxxxx=,ssl=false,abortConnect=False

Steps to Reproduce

No response

Important Factoids

No response

References

No response

[sinbai]

Hi @Poil thanks for opening this issue here. Unfortunately, I could not reproduce this issue using the above terraform configuration. After applying the above tf configuration, the result on Azure portal is as follows, could you please double check and provide more details?

[Poil]

Sorry, it's the output of Terraform that is wrong not in the portal !

[sinbai]

Hi @Poil ,thanks for your explanation. I have submitted PR to fix it. Could you please follow it for more updates?

[github-actions]

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.