From 46d692a42fb6357a0351cc66b8a08ef63583aae1 Mon Sep 17 00:00:00 2001 From: Vlad Vinogradsky Date: Tue, 25 Jun 2024 15:00:47 -0700 Subject: [PATCH 1/8] 0.45 release notes --- changelogs/api-management-service.md | 33 ++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/changelogs/api-management-service.md b/changelogs/api-management-service.md index d1b7864..47d6c16 100644 --- a/changelogs/api-management-service.md +++ b/changelogs/api-management-service.md @@ -1,5 +1,38 @@ # Azure API Management service changelog +## Release - API Management service: June, 2024 + +### ‼️ Breaking changes ‼️ + +- URL properties in the [Backend](https://learn.microsoft.com/rest/api/apimanagement/backend/create-or-update) entity no longer accept URLs containing query parameters. We've made the change to fix a bug. Please use [`set-query-parameter`](https://learn.microsoft.com/azure/api-management/set-query-parameter-policy) policy and [`backend.credentials.query`](https://learn.microsoft.com/rest/api/apimanagement/backend/create-or-update#backendcredentialscontract) to set query parameters. + +### New features, improvements, and changes + +- HTTP/2 connections are now drained and gracefully terminated before node restarts +- We added support for decryption keys to the [`validate-azure-ad-token`](https://learn.microsoft.com/azure/api-management/validate-jwt-policy) policy +- [`azure-openai-semantic-cache-lookup`](https://learn.microsoft.com/azure/api-management/azure-openai-semantic-cache-lookup-policy) and [`azure-openai-semantic-cache-store`](https://learn.microsoft.com/azure/api-management/azure-openai-semantic-cache-store-policy) policies now work in both V2 and Classic tiers. +- We've imprioved promt token estimation accuracy for GPT-4 models in the [`azure-openai-token-limit `](https://learn.microsoft.com/azure/api-management/azure-openai-token-limit-policy) policy + +### Fixes + +- We fixed an issue which caused GraphQL resolver runtime errors when primitive type fileds had null value +- We fixed a bug and stopped the fields of type array-of-objects from causing GraphQL resolver runtime errors +- Load balancer feature ... +- Expressions are now work as expected for in the `` elements in the [`validate-jwt`](https://learn.microsoft.com/azure/api-management/validate-jwt-policy) policy +- We fixed a bug that caused XML entities to be erroneously unescaped in the policy documents + +### Self-hosted developer portal releases + +- No new releases + +### Self-hosted gateway container image releases + +- [2.26.0](https://github.com/Azure/api-management-self-hosted-gateway/releases/tag/Container-v2.6.0) + +### Self-hosted gateway Helm chart releases + +- [1.10.0](https://github.com/Azure/api-management-self-hosted-gateway/releases/tag/v1.10.0) + ## Release - API Management service: May, 2024 ### New features, improvements, and changes From 7fd534d7384a550004f1e36de690f9d99d5a8560 Mon Sep 17 00:00:00 2001 From: Vlad Vinogradsky Date: Tue, 25 Jun 2024 15:26:20 -0700 Subject: [PATCH 2/8] Update api-management-service.md --- changelogs/api-management-service.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/changelogs/api-management-service.md b/changelogs/api-management-service.md index 47d6c16..0b0c641 100644 --- a/changelogs/api-management-service.md +++ b/changelogs/api-management-service.md @@ -2,14 +2,10 @@ ## Release - API Management service: June, 2024 -### ‼️ Breaking changes ‼️ - -- URL properties in the [Backend](https://learn.microsoft.com/rest/api/apimanagement/backend/create-or-update) entity no longer accept URLs containing query parameters. We've made the change to fix a bug. Please use [`set-query-parameter`](https://learn.microsoft.com/azure/api-management/set-query-parameter-policy) policy and [`backend.credentials.query`](https://learn.microsoft.com/rest/api/apimanagement/backend/create-or-update#backendcredentialscontract) to set query parameters. - ### New features, improvements, and changes - HTTP/2 connections are now drained and gracefully terminated before node restarts -- We added support for decryption keys to the [`validate-azure-ad-token`](https://learn.microsoft.com/azure/api-management/validate-jwt-policy) policy +- We added support for decryption keys to the [`validate-azure-ad-token`](https://learn.microsoft.com/azure/api-management/validate-azure-ad-token-policy) policy - [`azure-openai-semantic-cache-lookup`](https://learn.microsoft.com/azure/api-management/azure-openai-semantic-cache-lookup-policy) and [`azure-openai-semantic-cache-store`](https://learn.microsoft.com/azure/api-management/azure-openai-semantic-cache-store-policy) policies now work in both V2 and Classic tiers. - We've imprioved promt token estimation accuracy for GPT-4 models in the [`azure-openai-token-limit `](https://learn.microsoft.com/azure/api-management/azure-openai-token-limit-policy) policy @@ -19,7 +15,8 @@ - We fixed a bug and stopped the fields of type array-of-objects from causing GraphQL resolver runtime errors - Load balancer feature ... - Expressions are now work as expected for in the `` elements in the [`validate-jwt`](https://learn.microsoft.com/azure/api-management/validate-jwt-policy) policy -- We fixed a bug that caused XML entities to be erroneously unescaped in the policy documents +- We fixed a bug causing XML elements within Liquid templates in policy documents to be needlessly decoded +- URL properties in the [Backend](https://learn.microsoft.com/rest/api/apimanagement/backend/create-or-update) entity no longer accept URLs containing query parameters. We've made the change to fix a bug. Please use [`set-query-parameter`](https://learn.microsoft.com/azure/api-management/set-query-parameter-policy) policy and [`backend.credentials.query`](https://learn.microsoft.com/rest/api/apimanagement/backend/create-or-update#backendcredentialscontract) to set query parameters ### Self-hosted developer portal releases From 71eda84df927ea88b6bd1324ec03f28ea4905b50 Mon Sep 17 00:00:00 2001 From: Vlad Vinogradsky Date: Tue, 25 Jun 2024 15:45:54 -0700 Subject: [PATCH 3/8] Update api-management-service.md --- changelogs/api-management-service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/changelogs/api-management-service.md b/changelogs/api-management-service.md index 0b0c641..f399a3c 100644 --- a/changelogs/api-management-service.md +++ b/changelogs/api-management-service.md @@ -13,7 +13,6 @@ - We fixed an issue which caused GraphQL resolver runtime errors when primitive type fileds had null value - We fixed a bug and stopped the fields of type array-of-objects from causing GraphQL resolver runtime errors -- Load balancer feature ... - Expressions are now work as expected for in the `` elements in the [`validate-jwt`](https://learn.microsoft.com/azure/api-management/validate-jwt-policy) policy - We fixed a bug causing XML elements within Liquid templates in policy documents to be needlessly decoded - URL properties in the [Backend](https://learn.microsoft.com/rest/api/apimanagement/backend/create-or-update) entity no longer accept URLs containing query parameters. We've made the change to fix a bug. Please use [`set-query-parameter`](https://learn.microsoft.com/azure/api-management/set-query-parameter-policy) policy and [`backend.credentials.query`](https://learn.microsoft.com/rest/api/apimanagement/backend/create-or-update#backendcredentialscontract) to set query parameters @@ -30,6 +29,7 @@ - [1.10.0](https://github.com/Azure/api-management-self-hosted-gateway/releases/tag/v1.10.0) + ## Release - API Management service: May, 2024 ### New features, improvements, and changes From 327a49b725487793fd42abe7c4e9f0218a3bc5a8 Mon Sep 17 00:00:00 2001 From: Vlad Vinogradsky Date: Wed, 26 Jun 2024 09:15:12 -0700 Subject: [PATCH 4/8] Update api-management-service.md --- changelogs/api-management-service.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/changelogs/api-management-service.md b/changelogs/api-management-service.md index f399a3c..5e07778 100644 --- a/changelogs/api-management-service.md +++ b/changelogs/api-management-service.md @@ -19,7 +19,7 @@ ### Self-hosted developer portal releases -- No new releases +- [2.28.0](https://github.com/Azure/api-management-developer-portal/releases/tag/2.28.0) ### Self-hosted gateway container image releases @@ -29,7 +29,6 @@ - [1.10.0](https://github.com/Azure/api-management-self-hosted-gateway/releases/tag/v1.10.0) - ## Release - API Management service: May, 2024 ### New features, improvements, and changes From 00c9d8a4f4c14544d55cce8428ffc37175387a72 Mon Sep 17 00:00:00 2001 From: Vlad Vinogradsky Date: Wed, 26 Jun 2024 09:16:12 -0700 Subject: [PATCH 5/8] Update api-management-service.md --- changelogs/api-management-service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/changelogs/api-management-service.md b/changelogs/api-management-service.md index 5e07778..171a386 100644 --- a/changelogs/api-management-service.md +++ b/changelogs/api-management-service.md @@ -7,7 +7,7 @@ - HTTP/2 connections are now drained and gracefully terminated before node restarts - We added support for decryption keys to the [`validate-azure-ad-token`](https://learn.microsoft.com/azure/api-management/validate-azure-ad-token-policy) policy - [`azure-openai-semantic-cache-lookup`](https://learn.microsoft.com/azure/api-management/azure-openai-semantic-cache-lookup-policy) and [`azure-openai-semantic-cache-store`](https://learn.microsoft.com/azure/api-management/azure-openai-semantic-cache-store-policy) policies now work in both V2 and Classic tiers. -- We've imprioved promt token estimation accuracy for GPT-4 models in the [`azure-openai-token-limit `](https://learn.microsoft.com/azure/api-management/azure-openai-token-limit-policy) policy +- We've improved prompt token estimation accuracy for GPT-4 models in the [`azure-openai-token-limit `](https://learn.microsoft.com/azure/api-management/azure-openai-token-limit-policy) policy ### Fixes From 98fdd15455f3bf8ad2929f9ec30f48e79ab9c7c2 Mon Sep 17 00:00:00 2001 From: Vlad Vinogradsky Date: Wed, 26 Jun 2024 09:17:28 -0700 Subject: [PATCH 6/8] Update api-management-service.md --- changelogs/api-management-service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/changelogs/api-management-service.md b/changelogs/api-management-service.md index 171a386..67473b9 100644 --- a/changelogs/api-management-service.md +++ b/changelogs/api-management-service.md @@ -13,7 +13,7 @@ - We fixed an issue which caused GraphQL resolver runtime errors when primitive type fileds had null value - We fixed a bug and stopped the fields of type array-of-objects from causing GraphQL resolver runtime errors -- Expressions are now work as expected for in the `` elements in the [`validate-jwt`](https://learn.microsoft.com/azure/api-management/validate-jwt-policy) policy +- Expressions now work as expected for in the `` elements in the [`validate-jwt`](https://learn.microsoft.com/azure/api-management/validate-jwt-policy) policy - We fixed a bug causing XML elements within Liquid templates in policy documents to be needlessly decoded - URL properties in the [Backend](https://learn.microsoft.com/rest/api/apimanagement/backend/create-or-update) entity no longer accept URLs containing query parameters. We've made the change to fix a bug. Please use [`set-query-parameter`](https://learn.microsoft.com/azure/api-management/set-query-parameter-policy) policy and [`backend.credentials.query`](https://learn.microsoft.com/rest/api/apimanagement/backend/create-or-update#backendcredentialscontract) to set query parameters From b3974ac6ca6175224a7da1c611533eacbd387cb0 Mon Sep 17 00:00:00 2001 From: Vlad Vinogradsky Date: Wed, 26 Jun 2024 09:27:19 -0700 Subject: [PATCH 7/8] Update api-management-service.md --- changelogs/api-management-service.md | 1 + 1 file changed, 1 insertion(+) diff --git a/changelogs/api-management-service.md b/changelogs/api-management-service.md index 67473b9..5be96c9 100644 --- a/changelogs/api-management-service.md +++ b/changelogs/api-management-service.md @@ -16,6 +16,7 @@ - Expressions now work as expected for in the `` elements in the [`validate-jwt`](https://learn.microsoft.com/azure/api-management/validate-jwt-policy) policy - We fixed a bug causing XML elements within Liquid templates in policy documents to be needlessly decoded - URL properties in the [Backend](https://learn.microsoft.com/rest/api/apimanagement/backend/create-or-update) entity no longer accept URLs containing query parameters. We've made the change to fix a bug. Please use [`set-query-parameter`](https://learn.microsoft.com/azure/api-management/set-query-parameter-policy) policy and [`backend.credentials.query`](https://learn.microsoft.com/rest/api/apimanagement/backend/create-or-update#backendcredentialscontract) to set query parameters +- We fixed an issue preventing [backend load balancing feature](https://learn.microsoft.com/azure/api-management/backends?tabs=bicep#load-balanced-pool) from working properly with [`retry`](https://learn.microsoft.com/azure/api-management/retry-policy) policy ### Self-hosted developer portal releases From 7ba4b319a33d09199dab7ca6f56c3e17a9541de0 Mon Sep 17 00:00:00 2001 From: Vlad Vinogradsky Date: Wed, 26 Jun 2024 13:08:26 -0700 Subject: [PATCH 8/8] Update api-management-service.md --- changelogs/api-management-service.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/changelogs/api-management-service.md b/changelogs/api-management-service.md index 5be96c9..662aa10 100644 --- a/changelogs/api-management-service.md +++ b/changelogs/api-management-service.md @@ -8,6 +8,8 @@ - We added support for decryption keys to the [`validate-azure-ad-token`](https://learn.microsoft.com/azure/api-management/validate-azure-ad-token-policy) policy - [`azure-openai-semantic-cache-lookup`](https://learn.microsoft.com/azure/api-management/azure-openai-semantic-cache-lookup-policy) and [`azure-openai-semantic-cache-store`](https://learn.microsoft.com/azure/api-management/azure-openai-semantic-cache-store-policy) policies now work in both V2 and Classic tiers. - We've improved prompt token estimation accuracy for GPT-4 models in the [`azure-openai-token-limit `](https://learn.microsoft.com/azure/api-management/azure-openai-token-limit-policy) policy +- We've made [request tracing](https://learn.microsoft.com/azure/api-management/api-management-howto-api-inspector) more secure and it's now available in both Classic and V2 tiers +- Now customers can use Azure portal to [migrate](https://learn.microsoft.com/azure/api-management/migrate-stv1-to-stv2-vnet?#trigger-migration-of-a-network-injected-api-management-instance) their stv1 service instances to stv2 ### Fixes