Esta página se tradujo automáticamente. Leer el original en inglés.

Recipe

azure-api-management

Adds an API serving a model to an Azure API Management instance that already exists, rendered as Terraform for the azurerm provider: the API, its chat completions operation, the backend it forwards to and its policy. Reach for it where the instance exists and the Release is to configure the API; reach for the helm or compose reference where the API is configured outside the Release. It never creates the instance, so a Release without one creates it outside first. The policy sends each request to the backend, removes the caller's subscription key from what it forwards, and authenticates as infra.backend_authentication says; what an attached core/semantic-caching, core/period-budget, core/prompt-injection-shield or core/retry-policy sets is written into the same policy. Terraform authenticates to Azure with the credentials in the environment it runs in, and a provider key reaches the configuration only as the identifier of the Key Vault secret holding it, so the rendered files carry no credential. The azurerm provider, which does not plan without its features block, is configured in one file beside the boundary's root configuration, shared by every component there that declares it. So a Release that removes the last of them destroys what their modules created first: once the file is gone, Terraform has no provider configuration left to destroy those resources with. It needs hashicorp/azurerm 5 and terraform/postgres-flexible-server azurerm 4, so the two go in different terraform boundaries. Applying it is outside any build: whether the API then behaves as Microsoft documents is not observed by the compiler.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:0d8f694a00d74673661d8d1325280b3ac82c2ab95e2f9df318f7b312181da2d1
Publicado
2026-11-10T10:28:10Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • Oficialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:079c523dec66dcd400efae912b7da563868ab71dcfb3ce760237f081b7c5118d

Referencia en esta versión

oci://hub.aggrega.ai/recipe/terraform/azure-api-management:1.0.0
Destino
—
Implementa
core/gateway/azure-api-management:1.0.0

Proporciona

Plantillas de punteros deterministas que esta receta cablea para los consumidores.

NombrePlantilla
endpoint{{ .locals.gateway_url }}/{{ .infra.api_path }}
model{{ .values.model }}

Workload

No se declaró ninguna plantilla de carga de trabajo.

Variables locales

NombrePlantilla
api_name{{ .infra.api_path | replace "/" "-" }}
gateway_url{{ default (printf "https://%s.azure-api.net" .infra.api_management_name) (optional .infra "gateway_url" "") }}

Mapeo de valores

No se declaró ningún mapeo de valores.

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

  • implementaimplementacontrato compatible

    core/gateway/azure-api-management:1.0.0

    Todas las salidas obligatorias se satisfacen y cada salida proporcionada está nombrada en el contrato.

Usado por

Nada en el catálogo depende de esta entidad.

Referencia del concepto Recipe →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad