Schema.json format is not working- Azurerm_api_management_api_schema support config components and definitions #18394

[qasimalik786]

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

AzureRM Provider Version

3.65.0

Affected Resource(s)/Data Source(s)

azurerm_api_management_api_schema

Terraform Configuration Files

resource "azurerm_api_management_api_schema" "schema" {

  api_name = azurerm_api_management_api.amazon_api.name
  api_management_name = var.api_management_name
  resource_group_name = var.resource_group
  schema_id = local.amazon_schema_name
  content_type = "application/vnd.oai.openapi.components+json"
  components   = file("${path.module}/schema.json")
}



{
    "schema-bug-example": {
        "properties": {
            "Field2": {
                "description": "Field2",
                "type": "string"
            },
            "field1": {
                "description": "Field1",
                "type": "string"
            }
        },
        "required": [
            "field1",
            "Field2"
        ],
        "type": "object"
    }
}

Debug Output/Panic Output

terraform successfully apply the changes but in APIM(Azure) changes can't be applied.

Expected Behaviour

Schema.json should be applied to APIM

Actual Behaviour

No response

Steps to Reproduce

No response

Important Factoids

No response

References

No response

[rcskosir]

Thank you for opening this issue. It looks like the PR you referenced in your title #18394 has another open issue linked to it that may be the same issue you are experiencing, or similar, so I am linking for additional context #10066.