Terraform-provider-azurerm: azurerm_api_management.security boolean settings are the wrong way round

Created on 26 Mar 2019  ·  4Comments  ·  Source: terraform-providers/terraform-provider-azurerm

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 (and AzureRM Provider) Version

Terraform: 0.11.13
AzureRM: 1.23

Affected Resource(s)

  • azurerm_api_management

Terraform Configuration Files

resource "azurerm_api_management" "apim" {
  name                = "apim-${var.environment}"
  location            = "${azurerm_resource_group.apim.location}"
  resource_group_name = "${azurerm_resource_group.apim.name}"
  publisher_name      = "Sean"
  publisher_email     = "${var.apim_email}"
  sku {
    name     = "${var.apim_sku}"
    capacity = "${var.apim_capacity}"
  }
  security {
    # These parameters are the wrong way round - true means enable
    disable_backend_ssl30 = false
    disable_backend_tls10 = false
    disable_backend_tls11 = false
    disable_frontend_ssl30 = false
    disable_frontend_tls10 = false
    disable_frontend_tls11 = false
    disable_triple_des_chipers = false
  }
}

Expected Behavior


Setting a disable_ setting to true should disable the protocol.
Setting a disable_ setting to false should enable the protocol.

Actual Behavior


Setting a disable_ setting to true enables the protocol.
Setting a disable_ setting to false disables the protocol.

Steps to Reproduce

  1. terraform apply
breaking-change bug good first issue servicapi-management

Most helpful comment

I will work on this.

All 4 comments

I will work on this.

Hi @ReenuSaluja,

not sure if you already had some time to look into this issue. If so, can you please advice on how the solution will look afterwards ? It seems that just switching over to the expected behavior could cause impact.

This has been released in version 1.36.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 1.36.0"
}
# ... other configuration ...

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

Was this page helpful?
0 / 5 - 0 ratings