Feature request: AI Gateway connection support
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 229
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
📝 Description
I would like to use the new AI Gateway functionality via CAIRA.
There is a sample of this in Bicep code which can be found here https://github.com/azure-ai-foundry/foundry-samples/blob/main/infrastructure/infrastructure-setup-bicep/01-connections/apim/modules/apim-connection-common.bicep
🛰 Alternatives
No response
🚧 Potential Configuration / Desired Solution
foundry ref. architecture
variable "existing_api_management_resource_id" {
type = string
description = "Existing API Management service resource ID to use for agent API calls."
}
foundry project module
variable "api_management_connection" {
type = object({
name = string
resource_id = string
endpoint = string
path = string
})
default = null
description = "Configuration for API Management connection to AI Foundry Project."
}
resource "azapi_resource" "apim_connection" {
count = var.api_management_connection != null ? 1 : 0
type = "Microsoft.CognitiveServices/accounts/projects/connections@2025-06-01"
name = var.api_management_connection.name
parent_id = azapi_resource.ai_foundry_project.id
schema_validation_enabled = false
depends_on = [
azapi_resource.ai_foundry_project
]
body = {
name = var.api_management_connection.name
properties = {
category = "ApiManagement"
target = "${var.api_management_connection.endpoint}${var.api_management_connection.path}"
authType = "ApiKey"
isSharedToAll = false
credentials = {
key = "xxxx" # apim subscription key currently required for link, entra support underway.
}
metadata = {
ApiType = "Azure"
ResourceId = var.api_management_connection.resource_id
location = var.location
}
}
}
response_export_values = [
"identity.principalId"
]
}
📎 Additional context
No response
☑️ Acceptance Criteria
Working AIGateway connection to Azure API management
🔰 Code of Conduct
- I agree to follow this project's Code of Conduct.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the referenced foundry-samples Bicep file, infrastructure/infrastructure-setup-bicep/01-connections/apim/modules/apim-connection-common.bicep, and compare it with CAIRA’s Foundry project connection configuration. Use the proposed api_management_connection fields and Azure API Management metadata as the requirements; done means a working AI Gateway connection to Azure API Management.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, terraform
- Domain
- api, cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100