This page documents production updates to all Apigee software in 2022 and later. We recommend that users periodically check this list for any new announcements, or subscribe to this page using a feed reader to get notifications of updates.
What is a feed reader?
Really simple syndication (RSS) feed readers aggregate content from websites that you specify.
Feed reader notifications can be email-, browser-, desktop-, or mobile-based. Some readers are free, or have free versions, and some require a subscription.
A few examples:
More information on RSS:
See also:
You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or you can programmatically access release notes in BigQuery.
To get the latest product updates delivered to you, add the URL of this page to your
feed
reader, or add the feed URL directly: https://cloud.google.com/feeds/apigee-release-notes.xml
March 23, 2023
Apigee Integrated PortalOn March 23, 2023 we released an updated version of Apigee integrated portal.
Users are now able to enable the content security policy feature for their portal for Apigee and Apigee hybrid. Previously, this feature was available in Apigee Edge only.
Bug ID | Description |
---|---|
272794133 | When setting a user account to Inactive, a notice is now displayed indicating that this setting affects the login behavior only for built-in identity provider accounts. |
267502391 | Improved error messages for invalid input to various endpoints. |
265051231 | Default assets (images) added to a newly created portal used to show up as size 0px x 0px . Now they show their proper size. |
253037871 | Users are now able to enable the content security policy feature for their portal for Apigee and Apigee hybrid. Previously, this feature was available in Apigee Edge only. |
March 22, 2023
Apigee XOn March 22, we released an updated version of Apigee X.
Customize SSL certs for access routing when provisioning Apigee Pay-as-you-go organizations.
Users can now select existing self-managed SSL certs when customizing access routing during Apigee Pay-as-you-go provisioning. For more information, see Step 4: Customize access routing .
Receive Cloud console notifications when Pay-as-you-go provisioning completes.
While provisioning is in progress, users can navigate away from the Apigee provisioning page and monitor notifications in the Cloud console for updates when provisioning completes.
March 17, 2023
Apigee XOn March 17, we released an updated version of Apigee X (1-9-0-apigee-23).
Bug ID | Description |
---|---|
N/A | Upgraded infrastructure and libraries. |
March 16, 2023
API GatewayFixed issue where API Gateway used the IP address of the Google Cloud Load Balancer (GCLB) (specifically the address of the forwarding rule) to validate IP-restricted API keys in requests proxied by a GCLB. API gateway now correctly validates IP-restricted API keys using the IP address of the client calling the GCLB.
March 13, 2023
Apigee API hubOn March 13, 2023 Apigee API hub released a new version of the software.
FieldSet artifacts that are attached to an API are now displayed in the API overview page.
March 08, 2023
Apigee API hubOn March 8, 2023, the Apigee Registry API documents were updated to include the Google APIs Explorer panel.
The Google APIs Explorer has been added to the Apigee Registry API documents. The Try this method panel acts on real data and lets you try Google API methods without writing code.
March 02, 2023
Apigee UIOn March 2, 2023, we released an updated provisioning experience for Apigee users creating Pay-as-you-go organizations from the Apigee UI. All Apigee users creating new organizations with Pay-as-you-go billing can access the simplified onboarding experience, whether they are provisioning from the Apigee UI or the Google Cloud console.
March 01, 2023
Apigee ConnectorsOn March 1, 2023, we released updates to connectors for Apigee.
The IBM MQ connector now supports requestReply messages.
The Cloud Storage connector now supports the following actions for file operations:
- UploadObject
- DownloadObject
- MoveObject
- CopyObject
- DeleteObject
The MongoDB connector now supports the following actions:
- InsertDocument
- UpdateDocument
- DeleteDocument
- GetDocument
On March 1, 2023, we released an updated version of the Apigee UI.
Public preview release of the Apigee UI in the Google Cloud console
This release includes a new version of the Apigee UI that is integrated with the Google Cloud console. The new UI makes it easier to perform Apigee tasks that are managed in the Cloud console. We welcome your feedback on the new UI: click Send Feedback at the top of the UI.
For now, you can continue to use the classic Apigee UI if you wish: just click Back to Classic Apigee in the new UI.
The following tabs in the classic Apigee UI have not yet been implemented in the Apigee UI in the Cloud console, but they will be available there soon:
- Develop > Integrations
- API Security
- Monetization
- Analyze > API Metrics > Cache Performance,
- Analyze > API Metrics > Target Performance
- Analyze > Developers
- Analyze > End Users
- Publish > Portals
If you need to use these features, you can do so by switching to the classic Apigee UI.
This release will be rolled out over the next week, so you might not be able to view the new Apgee UI until the rollout is complete.
February 24, 2023
Apigee hybridhybrid v1.8.5
On February 24, 2023 we released an updated version of the Apigee hybrid software, v1.8.5.
For information on upgrading, see Upgrading Apigee hybrid to version 1.8.
Bug ID | Description |
---|---|
266594584 | Websocket was failing in asm 1.15. This was due to incompatible capitalization in variable names between the Anthos Service Mesh overlay.yaml file and the and the Envoy filter apigee-envoyfilter.yaml file. |
266411394 | Add support for Azure Front Door request headers to /healthz health check. |
260372012 | Requests failed with 500 response and keyvaluemap.service.ErrorDuringDecryption error after upgrade to Hybrid 1.8. Note: Fixed in Apigee hybrid 1.8.4 and newer. |
245619397 | In Apigee hybrid, fluentbit support now includes the NO_PROXY environment variable. |
181569522 | You can now create a new environment with the same name as a deleted environment without needing to perform manual clean-up tasks first. |
February 20, 2023
Apigee API hubOn February 20, 2023 Apigee API hub released a new version of the software.
Bug ID | Description |
---|---|
264686707 | Vertical scrollbars would not appear if the taxonomy and lifecycle stage tables overflowed the page. |
264409346 | The API list failed to load if there were over 1,000 APIs registered. |
February 14, 2023
Apigee hybridhybrid v1.7.6
On February 14, 2023 we released an updated version of the Apigee hybrid software, v1.7.6.
For information on upgrading, see Upgrading Apigee hybrid to version 1.7.
Bug ID | Description |
---|---|
268445095 | The validateOrg flag can be set to false to bypass upgrade validation errors when configuration includes HTTP Forward proxy. You can use this to avoid upgrade errors caused by HTTP proxy settings. |
262699558 | The watcher component no longer fails when using Kubernetes Secret to store hybrid service account secret. |
181569522 | You can now create a new environment with the same name as a deleted environment without needing to perform manual clean-up tasks first. |
218567150 | The ingress gateway is now configured to consistently preserve UUID in the x-request-id header. Note: This setting does have some impact on tracing in the ingress gateway. For more information, see pack_trace_reason in "UUID (proto)" in the envoy documentation. (Also fixed in Apigee hybrid v1.8.3) |
259264961 | Added support for ASM v1.15. Please see Known issue 266452840 |
February 09, 2023
Apigee IntegrationOn February 9, 2023 we released an updated version of the Apigee Integration.
Data Mapping Editor improvements
Transform expression changes:
- You can now add, modify, or remove a function or a function parameter in-between an existing transform expression without losing the subsequent transform functions in the expression.
- When applying a pre-defined transform function to a variable in the Data Mapping Editor, the function selection menu now displays the list of functions as per the return type of the preceding function or the data type of the preceding parameter.
Data Mapping Editor UI changes:
- Input rows are updated to display indent guides to improve readability and structure recognition.
- Mapping validation errors are now highlighted for each function in an Input row.
For more information, see Data Mapping editor.
Data Mapping Editor improvements
Transform expression changes:
- You can now add, modify, or remove a function or a function parameter in-between an existing transform expression without losing the subsequent transform functions in the expression.
- When applying a pre-defined transform function to a variable in the Data Mapping Editor, the function selection menu now displays the list of functions as per the return type of the preceding function or the data type of the preceding parameter.
Data Mapping Editor UI changes:
- Input rows are updated to display indent guides to improve readability and structure recognition.
- Mapping validation errors are now highlighted for each function in an Input row.
For more information, see Data Mapping editor.
February 08, 2023
Apigee XOn February 8, we released an updated version of Apigee X (1-9-0-apigee-21).
The VerifyAPIKey policy and the VerifyAccessToken
action of the OAuth2 policy now support CacheExpiryInSeconds
. Setting this variable enforces TTL on the cache and enables customization of the time period for cached token expiry.
Bug ID | Description |
---|---|
181569522 | Fixed the environment recreate scenario without manual cleanup. |
217173784 | The HMAC.policy-name.error variable is populated for HMAC failing policies. |
257268790 | Fixed bug where invalid proxy configuration halted Message Processor boot up. |
250638658 | Fixed the SetIntegrationRequest policy that fails if the JSON payload contains {foo} . |
265204739 | Set externalTrafficPolicy:local as default for Apigee X instances to mitigate 502 errors. |
N/A | Upgraded infrastructure and libraries. |
February 06, 2023
Apigee IntegrationOn February 6, 2023 we released an updated version of the Apigee Integration.
JavaScript task (Preview)
The JavaScript task lets you write custom JavaScript code snippets for your integration.
Using the JavaScript Editor, you can code complex data mapping logic for your integration, perform variable assignments, and add or modify integration variables.
For more information, see JavaScript task.
Delete integration
You can now delete an entire integration without the need to individually delete all the respective integration versions.
When you delete an integration, you permanently delete all the versions of that integration, including all the integration variables, configured triggers, tasks, and data mappings.
For more information, see Delete integrations.
JavaScript task
The JavaScript task lets you write custom JavaScript code snippets for your integration.
Using the JavaScript Editor, you can code complex data mapping logic for your integration, perform variable assignments, and add or modify integration variables.
For more information, see JavaScript task.
Delete integration
You can now delete an entire integration without the need to individually delete all the respective integration versions.
When you delete an integration, you permanently delete all the versions of that integration, including all the integration variables, configured triggers, tasks, and data mappings.
For more information, see Delete integrations.
New Overview page
A new Overview page is now introduced in Application Integration. It's the first place you land when opening Application Integration in your Google Cloud console, and helps you understand and get started with setting up Application Integration in your Google Cloud project.
February 01, 2023
Apigee hybridhybrid v1.9.0
On February 1, 2023 we released an updated version of the Apigee hybrid software, v1.9.0.
- For information on upgrading, see Upgrading Apigee hybrid to version 1.9.
- For information on new installations, see The big picture.
Kubernetes network policies
Starting in version 1.9, Apigee hybrid offers new Kubernetes network policies to secure Cassandra and Redis pods within an Apigee Hybrid cluster. See Configuring Kubernetes network policies.
CSI Backup and Restore
Starting with Apigee hybrid 1.9, you can back up and restore your hybrid data using CSI (Container Storage Interface) snapshots. CSI backup generates disk snapshots and stores them as encrypted data in cloud storage. See Cassandra CSI backup and restore.
Custom ingress access logs
Starting in version 1.9, Apigee hybrid offers custom log formats for the Apigee Ingress gateway. See Customize Ingress access logs.
Target separate ingress gateways to virtual hosts
Starting in version 1.9, Apigee hybrid you can control how separate Apigee Ingress gateways map to specific virtual hosts. See Targeting an Apigee ingress to a virtual host.
Support for customer-installed Anthos Service Mesh deprecated
Starting in version 1.9, Apigee hybrid only supports the Apigee Ingress gateway for ingress, and no longer supports customer-installed Anthos Service Mesh. See:
Bug ID | Description |
---|---|
266356206 | A jackson-databind library error was causing OAS Validation errors when loading applications. The jackson-databind libraries have been updated to correctly parse null vs NullMode values. (Fixed in Apigee hybrid v1.9.0) |
262616276 | Apigee hybrid v1.9 adds support for Kubernetes in AKS v1.24+. Also fixed in Apigee hybrid v1.8.4 and newer (Fixed in Apigee hybrid v1.9.0 and v1.8.4) |
260372012 | Requests failed with 500 response and keyvaluemap.service.ErrorDuringDecryption error after upgrade to Hybrid 1.8. Also fixed in Apigee hybrid v1.8.4 and newer (Fixed in Apigee hybrid v1.9.0 and v1.8.4) |
260324159 | Solved up to 30 minute delay proxy deployment due to socket closed error in synchronizer. (Fixed in Apigee hybrid v1.9.0) |
259738092 | Intermittent 404's were seen at the Apigee Ingress Gateway due to an inconsistent configuration delivery mechanism. (Fixed in Apigee hybrid v1.8.3) |
258699204 | The default memory requests and limits for metrics pods that were inadvertently changed in 1.8.x. have been fixed. Also fixed in Apigee hybrid v1.8.4 and newer (Fixed in Apigee hybrid v1.9.0 and v1.8.4) |
255677576 | In fresh installations with Apigee Ingress (instead of user-installed Anthos Service Mesh), the Apigee UI would sometimes show red (not working) status. This is because in certain circumstances Watcher did not send the correct deployment status due to using the wrong selector for the Apigee Ingress Gateway. (Fixed in Apigee hybrid v1.8.3) |
251435916 | Fixed an issue where in certain circumstances, MP pods would scale without traffic. (Fixed in Apigee hybrid v1.7.5) |
249144084 | Reuse existing target IPs if DNS resolution fail on DNS cache refresh. (Fixed in Apigee hybrid v1.8.1) |
245664917 | During the upgrade to Apigee hybrid 1.8.x, after running apigeectl init and confirming that check-ready succeeded, the Cassandra schema validation job was in an error state. Also fixed in Apigee hybrid v1.8.4 and newer (Fixed in Apigee hybrid v1.9.0 and v1.8.4) |
243880171 | Upgrade from Apigee hybrid v1.7 to v1.8 could fail when http_proxy was configured to DENY internal network traffic. (Fixed in Apigee hybrid v1.8.1) |
243717191 | Container restart no longer conflicts with the existing certificates. |
243599452 | Fixed indentation issue with ingress gateway annotations. (Fixed in Apigee hybrid v1.8.2) |
243167389 | Apigee now validates the length of ingressGateways[].name in overrides.yaml . TThe value of ingressGateways:name must meet the following requirements:
ingressGateways[].name in the Configuration property reference. (Fixed in Apigee hybrid v1.8.1) |
243158304 | 'ApigeeRouteConfig' no longer looks for a cert in the istio-system namespace. (Fixed in Apigee hybrid v1.9.0) |
241959053 | Fixed apigeectl parsing error for serviceaccountRef . (Fixed in Apigee hybrid v1.8.2) |
232529030 | Replaced the Logging fluentbit container environment variable http_proxy with HTTP__PROXY to maintain compatibility with fluentbit 1.8. (Fixed in Apigee hybrid v1.8.1) |
227212728 | Cassandra scripts now avoid writing data to the Pod Filesystem. (Fixed in Apigee hybrid v1.8.1) |
218567150 | The ingress gateway is now configured to consistently preserve UUID in the x-request-id header. This applies to both Apigee Ingress gateway and to the Istio ingress gateway when are using customer-installed Anthos Service Mesh. Note: This setting does have some impact on tracing in the ingress gateway. For more information, see pack_trace_reason in the "UUID (proto)" page in the envoy documentation. (Fixed in Apigee hybrid v1.8.3) |
Bug ID | Description |
---|---|
N/A | Upgraded to ASM 1.12.9 to address Istio and Go language vulnerabilities in an earlier version (CVE-2022-39278). For more information, see the Service Mesh security bulletin. (Fixed in Apigee hybrid v1.8.2) |
N/A | Upgraded to ASM 1.12.9 to address Istio and Go language vulnerabilities in an earlier version (CVE-2022-39278). For more information, see the Service Mesh security bulletin. (Fixed in Apigee hybrid v1.7.5) |
N/A | Miscellaneous Security updates and fixes. (Fixed in Apigee hybrid v1.7.4) |
262576073 | Security fix for apigee-watcher. Also fixed in Apigee hybrid v1.8.4 and newer (Fixed in Apigee hybrid v1.9.0 and v1.8.4) This addresses the following vulnerabilities: |
262574571 | Security fix for apigee-operators. Also fixed in Apigee hybrid v1.8.4 and newer (Fixed in Apigee hybrid v1.9.0 and v1.8.4) This addresses the following vulnerabilities: |
259290668 | Update Kubectl in the backup utility. (Fixed in Apigee hybrid v1.8.3) This addresses the following vulnerabilities:
|
256019598 | Security fix for Cassandra. Also fixed in Apigee hybrid v1.8.4 and newer (Fixed in Apigee hybrid v1.9.0 and v1.8.4) This addresses the following vulnerabilities: |
254862745, 249630685 | Security fix for apigee-diagnostics-runner and apigee-envoy . (Fixed in Apigee hybrid v1.8.3) This addresses the following vulnerabilities: |
254774193, 254773110 | Fix for vulnerability in apigee-diagnostics-collector , apigee-mart-server , and apigee-mint-task-scheduler . (Fixed in Apigee hybrid v1.8.3) This addresses the following vulnerability: |
254774167 | Fix for apigee-mart-server , apigee-mint-task-scheduler , apigee-runtime , and apigee-synchronizer . (Fixed in Apigee hybrid v1.8.3) This addresses the following vulnerabilities: |
254773838, 254773636, 254772551, 254771693 | Fix for vulnerability in apigee-diagnostics-collector , apigee-mart-server , apigee-mint-task-scheduler , apigee-runtime , and apigee-synchronizer . (Fixed in Apigee hybrid v1.8.3) This addresses the following vulnerabilities: |
254770883, 249633275, 249629782 | Security fixes for apigee-diagnostics-collector , apigee-mart-server , apigee-runtime , and apigee-synchronizer . (Fixed in Apigee hybrid v1.8.3) This addresses the following vulnerabilities:
|
254521563, 246970779 | Fix for golang vulnerability in Cassandra. (Fixed in Apigee hybrid v1.8.3) This addresses the following vulnerability: |
253693906 | Upgraded Prometheus to 2.39.1 to address vulnerabilities in an earlier version. (Fixed in Apigee hybrid v1.8.2) This addresses the following vulnerabilities: |
253498057 | Upgraded Fluent Bit to 1.9.9 to address vulnerabilities in an earlier version. (Fixed in Apigee hybrid v1.8.2) This addresses the following vulnerabilities: |
249635718, 249629771 | Security fixes for Apigee Connect and apigee-redis . (Fixed in Apigee hybrid v1.8.3) This addresses the following vulnerabilities: |
249633289 | Fix for apigee-prometheus-adapter . (Fixed in Apigee hybrid v1.8.3) This addresses the following vulnerabilities: |
248288668 | Fixes to address apigee-installer vulnerabilities. (Fixed in Apigee hybrid v1.8.2) |
247864229 | upgraded kube-rbac-proxy to v0.13.0 to address vulnerabilities in an earlier version. (Fixed in Apigee hybrid v1.8.2) |
240833499 | Security fix for gopkg.in/yaml.v3. (Fixed in Apigee hybrid v1.7.4) |
230369447 | Security fix for commons-codec (Fixed in Apigee hybrid v1.7.4) |
230368838 | Security fix for CVE-2018-10237, auto-value:guava. (Fixed in Apigee hybrid v1.7.4) |
230366823 | Security fix for jackson-databind. (Fixed in Apigee hybrid v1.7.4) |
230366589 | Security fix for CVE-2021-22696-cxf in cxf. (Fixed in Apigee hybrid v1.7.4) |
230366276 | Security fix for CVE-2021-22569. (Fixed in Apigee hybrid v1.7.4) |
229804717 | Security fix for apigee-envoy. (Fixed in Apigee hybrid v1.7.4) |
222772470, 220169963, 210116413 | Security fix for CVE-2021-38297: Updated Go language version. (Fixed in Apigee hybrid v1.8.1) |
222772341, 222772333, 222772261, 222771839 | Security fix for CVE-2022-23806: Updated Go language version. (Fixed in Apigee hybrid v1.8.2) |
202174499 | Fixed Vulnerability for protobuf-java and protobuf-java-util packages. (Fixed in Apigee hybrid v1.8.2) |
January 26, 2023
Apigee hybridhybrid v1.8.4
On January 26, 2023 we released an updated version of the Apigee hybrid software, v1.8.4. For information on upgrading, see Upgrading Apigee hybrid to version 1.8.
Bug ID | Description |
---|---|
262699558 | The watcher component failed when using Kubernetes Secret to store hybrid service account secret. |
262616276 | Added support for Kubernetes v1.24 and v1.25 |
260372012 | Requests failed with 500 response and keyvaluemap.service.ErrorDuringDecryption error after upgrade to Hybrid 1.8. |
258699204 | The default memory requests and limits for metrics pods that were inadvertently changed in 1.8.x. have been fixed. |
245664917 | During the upgrade to Apigee hybrid 1.8.x, after running apigeectl init and confirming that check-ready succeeded, the Cassandra schema validation job was in an error state. |
Bug ID | Description |
---|---|
262576073 | Security fix for apigee-watcher. This addresses the following vulnerabilities: ∙ CVE-2022-41716 ∙ CVE-2022-41715 ∙ CVE-2022-2880 ∙ CVE-2022-2879 |
262574571 | Security fix for apigee-operators. This addresses the following vulnerabilities: ∙ CVE-2022-41716 |
January 17, 2023
Apigee Integrated PortalOn January 17, 2023 we released an updated version of Apigee integrated portal.
Bug ID | Description |
---|---|
262260756 | We have updated the new account notification to administrators to read: "A new account was created by {{firstname}} {{lastname}} ({{email}}), for site {{siteurl}}. If you have enabled manual approval for new user accounts, this user will not be able to log in until you approve their account creation request by setting their status to 'active'." This is to highlight that they need to manually activate new accounts ONLY if they have enabled manual approval for new accounts. |
261788412 | Updated the version of GraphiQL used in the portal. |
January 11, 2023
Apigee UIOn January 11, 2023, we released an updated version of the Apigee UI.
GA release of the new Proxy Editor
The new Proxy Editor simplifies the process of adding policies to an API proxy, configuring those policies, and then deploying the proxy. See Introducing the new Proxy Editor.
January 10, 2023
Apigee IntegrationOn January 10, 2023 we released an updated version of the Apigee Integrations software.
Cloud Scheduler trigger (Preview)
The Cloud Scheduler trigger lets you schedule your integration executions for defined time periods or regular intervals across multiple regions. Cloud Scheduler triggers leverage the Cloud Scheduler services to provide a fully managed enterprise-grade cron job scheduler within Apigee Integration.
For more information, see Cloud Scheduler trigger.
Cloud Scheduler trigger
The Cloud Scheduler trigger lets you schedule your integration executions for defined time periods or regular intervals across multiple regions. Cloud Scheduler triggers leverage the Cloud Scheduler services to provide a fully managed enterprise-grade cron job scheduler within Application Integration.
For more information, see Cloud Scheduler trigger.
January 09, 2023
Apigee UIOn January 9, 2023, we released an updated version of the Apigee UI.
Specify an IP range with prefix /28 when creating a new instance
Previously, you could only specify an IP range with prefix /22 when creating an instance. This change makes it possible to specify /28 ranges as well as /22 ranges when creating an Apigee instance in the instance manager or the provisioning wizard.
Bug ID | Description |
---|---|
255609921 | Advanced API Security table rows now use links or span tags |
January 05, 2023
API GatewayBug ID | Description |
---|---|
266369520 | Fixed issue where gRPC requests to a gateway resulted in 400 responses following an ESPV2 upgrade. |
When calling a gateway using gRPC with transcoding, every field provided in a request message must contain a valid value. For every field included in the request message you must either specify a valid integer value or remove the field entirely.
January 04, 2023
Apigee ConnectorsOn January 04, 2023, we released the preview version of new connectors for Apigee.
December 26, 2022
Apigee IntegrationOn December 26, 2022 we released an updated version of the Apigee Integrations software.
Test without publishing an integration
You can now test your integration without the need to publish or create a new integration version. Testing an integration lets you experiment with the integration input variable values, and helps in identifying any faults in the integration connection flow before you finalize and publish the integration.
For more information, see Test and publish integrations.
Test without publishing an integration
You can now test your integration without the need to publish or create a new integration version. Testing an integration lets you experiment with the integration input variable values, and helps in identifying any faults in the integration connection flow before you finalize and publish the integration.
For more information, see Test and publish integrations.
December 22, 2022
Apigee ConnectorsOn December 22, 2022, we released the preview version of new connectors for Apigee.
The following new connectors are available in preview:
Connectors for Google services
Connectors for other applications
December 14, 2022
Apigee Integrated PortalOn December 14, 2022 we released an updated version of Apigee integrated portal.
Bug ID | Description |
---|---|
260725456 | The x-xss-protection header on portal runtime loading changed from value of "1;" to be "1; mode=block". |
254053443 | Fixed a bug to ensure that a Not found page is displayed whenever an invalid document path is navigated to in a portal. |
December 08, 2022
Apigee XOn December 8, we released an updated version of Apigee X.
GA release of Simplified Onboarding for Apigee X (Pay-as-you-go) in the Google Cloud console.
With this release, new Apigee customers using Pay-as-you-go pricing can quickly configure Apigee using a simplified onboarding flow accessible from the Google Cloud console.
- The new onboarding UI provides stepped navigation consistent with other products available in the console.
- Apigee X (Pay-as-you-go) provisioning is simplified but remains flexible. Default settings are provided, with the option to customize as needed.
- Improved contextual help streamlines decision-making during onboarding.
See Before you begin and Get started in the Cloud Console for more details on provisioning Apigee X with Pay-as-you-go pricing from the Google Cloud console.
December 05, 2022
Apigee hybridhybrid v1.8.3
On December 5, 2022 we released an updated version of the Apigee hybrid software, v1.8.3.
For information on upgrading, see Upgrading Apigee hybrid to version 1.8.
Bug ID | Description |
---|---|
259738092 | Intermittent 404's were seen at the Apigee Ingress Gateway due to an inconsistent configuration delivery mechanism. |
255677576 | In fresh installations with Apigee Ingress (instead of user-installed Anthos Service Mesh), the Apigee UI would sometimes show red (not working) status. This is because in certain circumstances Watcher did not send the correct deployment status due to using the wrong selector for the Apigee Ingress Gateway. |
218567150 | The ingress gateway is now configured to consistently preserve UUID in the x-request-id header. This applies to both Apigee Ingress gateway and to the Istio ingress gateway when are using customer-installed Anthos Service Mesh. Note: This setting does have some impact on tracing in the ingress gateway. For more information, see pack_trace_reason in the "UUID (proto)" page in the envoy documentation. |
Bug ID | Description |
---|---|
259290668 | Update Kubectl in the backup utility. This addresses the following vulnerabilities: ∙ CVE-2022-42004 ∙ CVE-2022-42003 ∙ CVE-2022-32189 ∙ CVE-2022-30635 ∙ CVE-2022-30633 ∙ CVE-2022-30632 ∙ CVE-2022-30631 ∙ CVE-2022-30630 ∙ CVE-2022-30580 ∙ CVE-2022-28327 ∙ CVE-2022-28131 ∙ CVE-2022-27664 ∙ CVE-2022-25857 ∙ CVE-2022-24921 ∙ CVE-2022-24675 ∙ CVE-2022-23773 ∙ CVE-2022-23772 ∙ CVE-2022-23635 ∙ CVE-2022-0391 ∙ CVE-2021-39156 ∙ CVE-2021-39155 ∙ CVE-2021-37137 ∙ CVE-2021-37136 ∙ CVE-2021-29482 ∙ CVE-2021-20190 ∙ CVE-2021-3121 ∙ CVE-2020-36518 ∙ CVE-2020-36189 ∙ CVE-2020-36188 ∙ CVE-2020-36187 ∙ CVE-2020-36186 ∙ CVE-2020-36185 ∙ CVE-2020-36184 ∙ CVE-2020-36183 ∙ CVE-2020-36182 ∙ CVE-2020-36181 ∙ CVE-2020-36180 ∙ CVE-2020-36179 ∙ CVE-2020-35728 ∙ CVE-2020-35491 ∙ CVE-2020-35490 ∙ CVE-2020-29652 ∙ CVE-2020-25649 ∙ CVE-2020-24750 ∙ CVE-2020-24616 ∙ CVE-2020-17516 ∙ CVE-2020-16845 ∙ CVE-2020-14195 ∙ CVE-2020-14062 ∙ CVE-2020-14061 ∙ CVE-2020-14060 ∙ CVE-2019-16869 ∙ CVE-2019-9674 ∙ CVE-2019-0205 ∙ CVE-2018-1320 ∙ CVE-2017-18640 ∙ CVE-2016-5397 |
254862745, 249630685 | Security fix for apigee-diagnostics-runner and apigee-envoy . This addresses the following vulnerabilities: ∙ CVE-2021-3999 ∙ CVE-2022-2068 |
254774167 | Fix for apigee-mart-server , apigee-mint-task-scheduler , apigee-runtime , and apigee-synchronizer . This addresses the following vulnerabilities: ∙ CVE-2022-42004 ∙ CVE-2022-42003 |
254773838, 254773636, 254772551, 254771693 | Fix for vulnerability in apigee-diagnostics-collector , apigee-mart-server , apigee-mint-task-scheduler , apigee-runtime , and apigee-synchronizer . This addresses the following vulnerabilities: ∙ CVE-2022-25857 ∙ CVE-2022-0239 ∙ CVE-2021-37136 ∙ CVE-2021-30468 ∙ CVE-2017-18640 |
254774193, 254773110 | Fix for vulnerability in apigee-diagnostics-collector , apigee-mart-server , and apigee-mint-task-scheduler . This addresses the following vulnerability: ∙ CVE-2022-2048 |
254770883, 249633275, 249629782 | Security fixes for apigee-diagnostics-collector , apigee-mart-server , apigee-runtime , and apigee-synchronizer . This addresses the following vulnerabilities: ∙ CVE-2022-42889 ∙ CVE-2022-42004 ∙ CVE-2022-42003 ∙ CVE-2022-40150 ∙ CVE-2022-40149 ∙ CVE-2022-38752 ∙ CVE-2022-38751 ∙ CVE-2022-38750 ∙ CVE-2022-38749 ∙ CVE-2022-25857 ∙ CVE-2022-3171 ∙ CVE-2022-2097 ∙ CVE-2022-2068 ∙ CVE-2022-2048 ∙ CVE-2022-2047 ∙ CVE-2022-1292 ∙ CVE-2021-31684 ∙ CVE-2021-29425 ∙ CVE-2021-27568 ∙ CVE-2020-13936 ∙ CVE-2020-8908 ∙ CVE-2019-18276 ∙ CVE-2018-10237 ∙ CVE-2017-18640 |
254521563, 246970779 | Fix for golang vulnerability in Cassandra. This addresses the following vulnerability: ∙ CVE-2017-5929 |
249635718, 249629771 | Security fixes for Apigee Connect and apigee-redis . This addresses the following vulnerabilities: ∙ CVE-2022-32189 ∙ CVE-2022-30635 ∙ CVE-2022-30633 ∙ CVE-2022-30632 ∙ CVE-2022-30631 ∙ CVE-2022-30630 ∙ CVE-2022-30580 ∙ CVE-2022-28327 ∙ CVE-2022-28131 ∙ CVE-2022-27664 ∙ CVE-2022-24921 ∙ CVE-2022-24675 ∙ CVE-2022-23773 ∙ CVE-2022-23772 |
249633289 | Fix for apigee-prometheus-adapter . This addresses the following vulnerabilities: ∙ CVE-2022-21698 ∙ CVE-2022-1996 |
November 29, 2022
Apigee IntegrationOn November 29, 2022 we released an updated version of the Apigee Integrations software.
Integration variable color code
The color codes of all the integration variable data types is removed and now changed to a single uniform color. Integration variables will no longer be color coded (green, blue, orange) based on their data type.
See Format of an integration variable.
Data Mapping editor
- The background color of the Input and Output row is changed to a single uniform color.
- Input rows are updated to add line breaks and indentations according to the use of mapping functions to improve readability and structure recognition.
- A confirmation dialog is displayed before proceeding to delete an entire Input row.
See Data Mapping editor.
November 23, 2022
Apigee IntegrationOn November 23, 2022 we released an updated version of the Apigee Integrations software.
Bug ID | Description |
---|---|
250638658 | Updated the behaviour of the SetIntegrationRequest policy to identify payload parameter strings enclosed within $# and #$ as flow variables. SetIntegrationRequest policy payload parameter strings enclosed within |
November 18, 2022
Apigee XOn November 18, 2022, we released an updated version of Apigee X (1-9-0-apigee-16).
Bug ID | Description |
---|---|
257268790 | There is an edge case scenario where an invalid resource or bundle configuration resulting in unhandled exception will result in failure that leads to restart of runtime pods or bootup of new runtime pods. |
November 14, 2022
Apigee MonetizationOn November 14, 2022 we released an updated version of the Apigee Monetization software.
Added support for a new recurring fees
Apigee X now supports optional recurring fees charged to API developers. For more information on fees, see Understanding billing.
November 10, 2022
Apigee Integrated PortalOn November 10, 2022 we released an updated version of Apigee integrated portal.
Bug ID | Description |
---|---|
246636016 | Updated the handling of linked or uploaded empty specification files for API catalog items, and added a meaningful error message. |
226406073 | In the portal list view, changed column Last Published to Created. Sorting is by oldest portal at top. |
182687440 | Updated the file filter for icon upload so you can choose and upload .ico files. |
153886771 | Fixed an issue with identity provider configuration where SAML certificate data would not correctly render after initial upload. |
On November 10, 2022 we released an updated version of the Apigee Monetization software.
Added support for a new setup fee
Apigee X now supports an optional setup fee charged to new API developers. For more information on fees, see Understanding billing.
November 04, 2022
Apigee IntegrationOn November 4, 2022 we released an updated version of the Apigee Integration software.
US multi-region (us) for Apigee Integration is deprecated. Use us-east1, us-west1, or us-central1 locations instead
As of November 10, 2022, you can no longer create an integration in the US multi-region (us) location. Any existing integration running in US multi-region (us) will be stopped on or after January 10, 2023.
It's recommended that you perform the following actions before January 10, 2023:
Clone your existing integrations to us-east1, us-west1, us-central1, or any of the supported regions. For information about how to clone an integration, see Clone integrations.
Migrate your existing integration proxies to us-east1, us-west1, us-central1, or any of the supported regions. You can do this by manually updating the
IntegrationRegion
child element in the SetIntegrationRequest policy.
On November 4, 2022 we released an updated version of Apigee X.
Apigee support for using Private Service Connect (PSC) for client-to-Apigee (northbound) traffic is now GA. In addition, we now support using PSC for northbound routing in multi-region configurations. For details, see Expanding Apigee to multiple regions. See also Northbound networking with Private Service Connect and Migrate northbound routing to Private Service Connect.
November 02, 2022
Apigee hybridhybrid v1.7.5
On November 2, 2022 we released an updated version of the Apigee hybrid software, v1.7.5.
For information on upgrading, see Upgrading Apigee hybrid to version 1.7.
Bug ID | Description |
---|---|
251435916 | Fixed an issue where in certain circumstances, MP pods would scale without traffic. |
241959053 | Fixed apigeectl parsing error for serviceaccountRef . |
Bug ID | Description |
---|---|
253693906 | Upgraded Prometheus to 2.39.1 to address vulnerabilities in an earlier version. This change addresses the following vulnerabilities: ∙ CVE-2022-24675 ∙ CVE-2022-27664 ∙ CVE-2022-28131 ∙ CVE-2022-28327 ∙ CVE-2022-30580 ∙ CVE-2022-30630 ∙ CVE-2022-30631 ∙ CVE-2022-30632 ∙ CVE-2022-30633 ∙ CVE-2022-30635 ∙ CVE-2022-32189 |
253498057 | Upgraded Fluent Bit to 1.9.9 to address vulnerabilities in an earlier version. This change addresses the following vulnerabilities: ∙ CVE-2022-1292 ∙ CVE-2022-2068 ∙ CVE-2021-3999 ∙ CVE-2022-23218 ∙ CVE-2022-23219 ∙ CVE-2022-25013 ∙ CVE-2021-33574 ∙ CVE-2018-12886 ∙ CVE-2022-0778 |
248288668 | Fixes to address apigee-installer vulnerabilities. |
247864229 | upgraded kube-rbac-proxy to v0.13.0 to address vulnerabilities in an earlier version. |
N/A | Upgraded to ASM 1.12.9 to address Istio and Go language vulnerabilities in an earlier version (CVE-2022-39278). For more information, see the Service Mesh security bulletin. |
October 27, 2022
Apigee API hubOn October 27, 2022 Apigee API hub released a new version of the software.
A link to the Settings page has been added to the APIs list page.
Bug ID | Description |
---|---|
254505866 | Provisioning API hub using the UI failed if you selected a region other than the following: asia-east1 , asia-southeast1 , europe-west1 , europe-west4 , us-central1 , us-east1 , us-west1 , us-west4 . |
On October 27, 2022 we released an updated version of Apigee X.
This release contains the General Acceptance (GA) release of Advanced API Security, which:
- Detects unwanted requests sent to your APIs, including attacks by bots or other malicious agents.
- Evaluates the security of your API configurations and provides recommendations for improvements.
Advanced API Security is a paid add-on to Apigee. You can try out Advanced API Security for free in any trial org—follow the procedure described in Enable Advanced API Security. Contact Apigee to learn more.
hybrid v1.8.2
On October 27, 2022 we released an updated version of the Apigee hybrid software, v1.8.2.
For information on upgrading, see Upgrading Apigee hybrid to version 1.8.
Bug ID | Description |
---|---|
253693906 | Upgraded Prometheus to 2.39.1 to address vulnerabilities in an earlier version. This change addresses the following vulnerabilities: ∙ CVE-2022-24675 ∙ CVE-2022-27664 ∙ CVE-2022-28131 ∙ CVE-2022-28327 ∙ CVE-2022-30580 ∙ CVE-2022-30630 ∙ CVE-2022-30631 ∙ CVE-2022-30632 ∙ CVE-2022-30633 ∙ CVE-2022-30635 ∙ CVE-2022-32189 |
253498057 | Upgraded Fluent Bit to 1.9.9 to address vulnerabilities in an earlier version. This change addresses the following vulnerabilities: ∙ CVE-2022-1292 ∙ CVE-2022-2068 ∙ CVE-2021-3999 ∙ CVE-2022-23218 ∙ CVE-2022-23219 ∙ CVE-2022-25013 ∙ CVE-2021-33574 ∙ CVE-2018-12886 ∙ CVE-2022-0778 |
248288668 | Fixes to address apigee-installer vulnerabilities. |
247864229 | upgraded kube-rbac-proxy to v0.13.0 to address vulnerabilities in an earlier version. |
N/A | Upgraded to ASM 1.12.9 to address Istio and Go language vulnerabilities in an earlier version (CVE-2022-39278). For more information, see the Service Mesh security bulletin. |
October 24, 2022
Apigee XOn October 24, 2022, we released an updated version of Apigee X (1-9-0-apigee-5).
Some runtime error messages have been improved with a reason code. To display only the error codes with a reason code, scroll down to Search and type reason
. The error catalog filters the view.
Bug ID | Description |
---|---|
252818300 | Fixed issue with failing web socket connections. |
249580739 | This feature introduces a new filter-based mechanism to display API products. |
249521773 | Endpoint attachment ID naming convention change. The ID must start with a lowercase letter followed by up to 31 lowercase letters, numbers, or hyphens, and cannot end with a hyphen. The minimum length is 2. See Create an endpoint attachment. |
249069616 | Fixed issue where error in DebugSession could interrupt runtime flow. |
248631925 | The Developer List API has been enhanced to support pagination in a Google-wide consistent pattern. |
247540503 | Race condition with encryption key lookup causing KVM lookup failures. |
246774745 | io.timeout.millis not honored, causing 504 Gateway timeout for dynamic targets. |
246193561 | Disabling/Destroying of customer cloud KMS key impacted the runtime after 5 minutes and data that was encrypted with the key could not be accessed by Apigee data plane. |
241786534 | MART is able to send logs to UDCA successfully now. |
240618523 | Dynamically setting target.url now supports websocket protocols (ws and wss ) |
218567150 | X-request-id headers modified at 14th character. |
206879901 | Fixed issue where Response headers were not visible from debug screen. |
173566787 | Message Processors behavior is changed. Message Processors will now reuse existing target IP addresses once if DNS resolution fails during DNS cache refresh |
159599332 | The flow variable servicecallout.requesturi reflects appropriately if the URI is constructed using multiple variables. |
N/A | Upgraded infrastructure and libraries |
Bug ID | Description |
---|---|
204965286 | Security fix for CVE-2022-25647 |
193613381 | Security fix for CVE-2021-21290 in netty-transport |
Known issue: 257268790 - Unhandled exception results in failure that leads to restart or bootup of new runtime pods.
October 19, 2022
Apigee Integrated PortalOn October 19, 2022 we released an updated version of Apigee integrated portal.
Bug ID | Description |
---|---|
239424786 | When reusing your portal custom domain with other sites, the cookies for the domain can get larger. This fix allows you to send cookies up to 16K in size, up from the previous 8K limit. |
237181283 | Pressing the enter button in the input field of Portals > Accounts > Authentication > Account creation & sign in no longer opens a file explorer window. |
233933177 | The email notification field for new account creation can be only a single email address, and not multiple email addresses separated by a delimiter (ie , space or tab). This fix adds validation on the client side to enforce this limitation. |
October 17, 2022
Apigee API hubOn October 17, 2022 Apigee API hub released a new version of the software.
New UI provisioning wizard
Added a wizard to the API hub UI to provide a simpler provisioning process.
Updated the layout of the score card display in the API overview tab.
See: Scorecard
October 06, 2022
Apigee XOn October 6, 2022, Apigee announced the GA launch of Cloud Monitoring for Apigee gateway node usage for Pay-as-you-go customers.
The availability of Apigee gateway node usage metrics in Cloud Monitoring enables Pay-as-you-go customers to view node usage, create dashboards, and configure alerting policies using Cloud Monitoring interfaces. For more information, see View usage and estimate your bill.
October 04, 2022
Apigee IntegrationOn October 4, 2022 we released an updated version of the Apigee Integration software.
Apigee Integration trials
Starting with this release, Apigee Integration trials (eval org) is available in Application Integration. Users in a newly provisioned Apigee eval org will be redirected to Application Integration when they open Integrations in Apigee. You can continue using the Apigee proxies (created in the eval org) with the integrations created in Application Integration.
October 01, 2022
Apigee hybridhybrid new installation experience public preview
On September 30, 2022 we released the public preview of the new Apigee hybrid installation experience.
Overview
The new Apigee hybrid installation experience provides a Kubernetes way of installing Apigee components using kubectl
. The enhanced validations and visibility of the components being installed provides better debuggability and improves the overall install process.
An install script, apigee-hybrid-setup.sh
, provides an easy tool for basic installation. You can use that to create your hybrid installation and then modify it to fit your needs with kubectl
, or you can create your hybrid installation from scratch using kubectl
. All Apigee hybrid configuration properties are stored in yaml files, one for each major component. This allows much more granular control of your hybrid installation on your Kubernetes environment.
Links
Preview release
The new Apigee hybrid installation experience and its documentation are part of a preview release. Apigee does not warranty the software or the procedures in this preview. The software and documentation are subject to change without notice.
September 29, 2022
Apigee hybridhybrid v1.8.1
On September 29, 2022 we released an updated version of the Apigee hybrid software, v1.8.1.
For information on upgrading, see Upgrading Apigee hybrid to version 1.8.
Bug ID | Description |
---|---|
249144084 | Reuse existing target IPs if DNS resolution fail on DNS cache refresh. |
243880171 | Upgrade from Apigee hybrid v1.7 to v1.8 could fail when http_proxy was configured to DENY internal network traffic. |
243717191 | Container restart no longer conflicts with the existing certificates. |
243599452 | Fixed indentation issue with ingress gateway annotations. |
243167389 | Apigee now validates the length of ingressGateways[].name in overrides.yaml . TThe value of ingressGateways:name must meet the following requirements:
ingressGateways[].name in the Configuration property reference. |
241959053 | Fixed apigeectl parsing error for serviceaccountRef . |
232529030 | Replaced the Logging fluentbit container environment variable http_proxy with HTTP__PROXY to maintain compatibility with fluentbit 1.8. |
227212728 | Cassandra scripts now avoid writing data to the Pod Filesystem. |
Bug ID | Description |
---|---|
222772470, 220169963, 210116413 | Security fix for CVE-2021-38297: Updated Go language version. |
222772341, 222772333, 222772261, 222771839 | Security fix for CVE-2022-23806: Updated Go language version. |
202174499 | Fixed Vulnerability for protobuf-java and protobuf-java-util packages. |
September 28, 2022
Application IntegrationApplication Integration Preview Release
Application Integration is now available in preview. Application Integration is an Integration-Platform-as-a-Service (iPaaS) solution in Google Cloud that offers a comprehensive set of core integration tools to connect and manage the multitude of applications and data required to support various business operations.
For more information about the Application Integration features and functionalities, see Application Integration documentation.
September 26, 2022
Apigee API hubOn September 26, 2022 Apigee API hub released a new version of the software.
Bug ID | Description |
---|---|
248598430 | Scorecard display did not select the latest spec by default when the recommended deployment pointed to a spec with no scorecard. |
Availability of scripts to recreate Apigee instances created before January 25, 2022.
If you have an Apigee instance that was created before January 25, 2022, Apigee recommends that you replace it with a new instance. If you do not recreate the older instance, you may experience scaling issues and the number of environments you can add to an instance will continue to be limited to 10.
For more information and detailed instructions, see Recreating an Apigee instance with zero downtime
September 19, 2022
Apigee API hubOn September 19, 2022 Apigee API hub released a new version of the software.
Scorecard added to Apigee API hub API overview page
The scorecard allows you to display score or health information about your APIs on the API overview page.
The default scorecard configuration uses OpenAPI v2 and OpenAPI v3 specs and is analyzed using the Spectral linter to generate a Lint summary.
Specify whether the scorecard is displayed or hidden on the Settings page.
Help links added to Apigee API hub blank APIs list page
If there are no APIs registered, the APIs list page will display links pointing to API registration documentation.
September 14, 2022
Apigee XOn September 14, 2022 we released an updated version of the Apigee X software.
When using local development with Apigee in VS Code, the following pre-release features are available as part of the Insiders build (v1.21.0 and higher):
September 12, 2022
Apigee Integrated PortalOn September 12, 2022 we released an updated version of Apigee integrated portal.
Bug ID | Description |
---|---|
237412458 | Fixed an issue where some SMTP settings were not migrated to an upgraded portal. |
235634994 | Implemented a minor security fix to block content spoofing in the API search page. |
233407912 | When creating a new App key for products that have been set to manual approval, but have already been approved, the new key will "auto" approve and not have to go through the approval process again. |
September 09, 2022
Apigee XOn September 09, 2022, we released an updated version of Apigee X.
With this release, Apigee support for Private Service Connect (PSC) is GA. PSC allows you to privately connect Apigee to target services running across VPC networks in addition to the peered network. For more information, see Southbound networking patterns.
September 06, 2022
Apigee API hubOn September 6, 2022 Apigee hub released a new version of the software.
API hub has been upgraded to use a later version of the Registry API open-sourced project. See v0.5.6 on GitHub for details.
Bug ID | Description |
---|---|
N/A | Multiple fixes as listed at v0.5.6 Changelog on GitHub. |
September 02, 2022
Apigee hybridhybrid v1.7.4
On September 2, 2022 we released an updated version of the Apigee hybrid software, v1.7.4.
For information on upgrading, see Upgrading Apigee hybrid to version 1.7.
Bug ID | Description |
---|---|
232529030 | Replaced the Logging fluentbit container environment variable http_proxy with HTTP_PROXY to maintain compatibility with fluentbit 1.8. |
Bug ID | Description |
---|---|
240833499 | Security fix for gopkg.in/yaml.v3. |
230369447 | Security fix for commons-codec |
230368838 | Security fix for CVE-2018-10237, auto-value:guava. |
230366823 | Security fix for jackson-databind. |
230366589 | Security fix for CVE-2021-22696-cxf in cxf. |
230366276 | Security fix for CVE-2021-22569. |
229804717 | Security fix for apigee-envoy. |
N/A | Miscellaneous Security updates and fixes. |
September 01, 2022
Apigee IntegrationOn September 01, 2022 we released an updated version of the Apigee Integration software.
Region support for integration endpoint
Region support when creating an integration using a proxy. You can now specify the region of the integration in a proxy and use that region to generate a regionalised integration endpoint. For more information, see Getting started with Apigee Integration and Apigee proxy Integration targets.
Region support in SetIntegrationRequest policy. Using the <IntegrationRegion> element, you can now specify the region of your integration in the SetIntegrationRequest policy.
Note: <IntegrationRegion> is a mandatory element in the SetIntegrationRequest policy and applies to any new proxies that are created from this release onwards. If there is no <IntegrationRegion> provided in the policy, Apigee will throw an error and continue execution using the Apigee runtime region.
For more information, see SetIntegrationRequest policy.
August 30, 2022
Apigee XOn August 30, 2022, Apigee announced the GA launch of Pay-as-you-go pricing, a consumption-based model for Google's Apigee Platform.
When you use Pay-as-you-go pricing for Apigee, you are charged for the following:
- The number of Apigee gateway nodes in the Apigee organization
- The number of API requests processed by Apigee Analytics services
- The amount of network usage
For more information, see the Pay-as-you-go overview and the Pay-as-you-go Example pricing.
With this release, the Apigee Pay-as-you-go pricing model includes a maximum Apigee gateway node count of 1,000 across all environments in a region.
August 25, 2022
Apigee API hubOn August 25, 2022 Apigee hub released a new version of the software.
API hub has been upgraded to use a later version of the Registry API open-sourced project. See v0.5.5 on GitHub for details.
Bug ID | Description |
---|---|
N/A | Multiple fixes as listed at v0.5.5 Changelog on GitHub. |
August 23, 2022
Apigee API hubOn August 23, 2022 Apigee hub released a new version of the software.
API hub has been upgraded to use a later version of the Registry API open-sourced project. See v0.5.4 on GitHub for details.
Bug ID | Description |
---|---|
N/A | Multiple fixes as listed at v0.5.4 Changelog on GitHub. |
On August 23, 2022, we released an updated version of the Apigee UI.
With this release, the Apigee UI will display the new version of the Proxy Editor by default.
In this release, you can view both the visual editor and the text editor at the same time in the Develop view, without having to manually switch between the two. You can also resize the display area of either editor to view it more easily. See Change the target endpoint for a description of the changes to the editor layout.
August 22, 2022
Apigee XOn August 22, 2022, we released an updated version of Apigee X (1-8-0-apigee-33).
Bug ID | Description |
---|---|
N/A | Upgraded infrastructure and libraries |
Value of io.timeout.millis
is not honored when used with multiple dynamic targets.
If a proxy sets two or more io.timeout.millis
values in two or more flows using the same target host, only one io.timeout.millis
value is honored.
hybrid v1.8.0
On August 22, 2022 we released an updated version of the Apigee hybrid software, v1.8.0.
For information on upgrading, see Upgrading Apigee hybrid to version 1.8.
Apigee Ingress gateway
Starting in version 1.8, Apigee hybrid offers a new feature to manage the ingress gateway for your hybrid installation, Apigee ingress gateway. Anthos Service Mesh is no longer a prerequisite for hybrid installation. With Apigee ingress gateway, Apigee will stop supplying routing configuration to Anthos Service Mesh. See Managing Apigee ingress.
ORG-level UDCA
Apigee hybrid now supports setting UDCA at the org level instead of at the environment level. See orgScopedUDCA
in the Configuration property reference.
Support for newer versions of Anthos, Anthos Service Mesh, and Kubernetes
Starting in version 1.8, Apigee hybrid supports Anthos version 1.12, Anthos Service Mesh version 1.13, and Kubernetes version 1.23 on specific platforms. See Apigee hybrid supported platforms and versions for details.
KVM pagination
Apigee hybrid now supports KVM pagination (introduced in Apigee X on March 10, 2022). See REST Resource: organizations.keyvaluemaps
and REST Resource: v1.organizations.environments.keyvaluemaps
.
apigeectl
now supports the --v
option to set the log verbosity level
Starting in version 1.8, apigeectl
includes a --v
option to set log verbosity levels in the format --v=int
, for example apigeectl apply --v=5
. This option replaces the --verbose
option (now deprecated). This is the same as the kubectl
--v
option. See apigeectl
for details.
tools/apigee-pull-push.sh
includes a –list
option to list all images
Starting in version 1.8, The tools/apigee-pull-push.sh
utility has a --list
or -l
option that will list all images in the gcr repo. See apigee-pull-push.sh
for details.
Bug ID | Description |
---|---|
239854141 | apigee-pull-push.sh now uses gcr source repositories. (Fixed in Apigee hybrid v1.8.0) |
238370197 | Fixed an issue where the timeTaken variable's value could sometimes be calculated incorrectly. (Fixed in Apigee hybrid v1.7.3) |
236399482 | Added support for ASM v1.13. (Fixed in Apigee hybrid v1.7.2) |
236129944 | Fixed the controller crashloopbackoff due to null pointer issue. (Fixed in Apigee hybrid v1.6.9) |
236129944 | Fixed the controller crashloopbackoff resulting from null pointer. (Fixed in Apigee hybrid v1.7.2) |
234620567 | Fix logger issue in Anthos BareMetal with CentOS. (Fixed in Apigee hybrid v1.6.9) |
234355351 | Fixed issue with message processor pods restarting frequently. Added backoff polling task for Cloud KMS key listener. The listener is paused only when the flush policy is met. (Fixed in Apigee X, June 21, 2022) |
233349518 | Fixed "Invalid Resource" error generated for job/apigee-resources-install . (Fixed in Apigee hybrid v1.7.1) |
233094108 | Fixed Stacktrace truncation in runtime containers to support proxy diagnosis. (Fixed in Apigee hybrid v1.7.2) |
232977937 | Fixed an issue where deployment would become stuck on "Applying routing changes on" for multiple ingress gateways. (Fixed in Apigee hybrid v1.7.1) |
231313050 | Fixed issue causing Apigee logger pod to remain in crashloopbackoff state. (Fixed in Apigee hybrid v1.7.2) |
229824389 | Fixed an issue in hybrid 1.7.0 where the output apigeectl init could be generated in the wrong order. (Fixed in Apigee hybrid v1.7.1) |
229804717 | Fixed upgrade envoy to use distroless v1.22.0. (Fixed in Apigee hybrid v1.7.1) |
229639530 | Fixed an error harmonizing the container process ID to use Apigee ID for Hybrid on OpenShift. (Fixed in Apigee hybrid v1.7.1) |
228855520 | Upgraded support for ASM version 1.13. (Fixed in Apigee X, May 9, 2022) |
227600373 | Fixed an installation issue with Cassandra. (Fixed in Apigee hybrid v1.6.7) |
227538469 | Fixed an issue where configuration actions would write logs to the pod file system. (Fixed in Apigee hybrid v1.7.1) |
226964206 | MART, runtime and synchronizer would write to the pod file system. (Fixed in Apigee hybrid v1.7.1) |
226464960 | Apigee hybrid fresh installations on OpenShift 4.6 and 4.8 would fail. (Fixed in Apigee hybrid v1.6.7) |
225939342 | Fixed an error where deployment status would show as "Applying routing changes on {env}". (Fixed in Apigee hybrid v1.7.1) |
225198475 | Fixed an issue where resource reference changes could not be detected. (Fixed in Apigee hybrid v1.7.1) |
225169066 | Cassandra database backup and restore was not working when http_proxy is enabled under certain circumstances. (Fixed in Apigee hybrid v1.5.10) |
225081332 | Fixed allow privileged pods issue. (Fixed in Apigee hybrid v1.7.1) |
224620542 | On some Kubernetes platforms, logging would fail without adding an empty directory for the logs. (Fixed in Apigee hybrid v1.6.7) |
223081301 | Fixed organization-level UDCA incorrect http-proxy secret name. (Fixed in Apigee hybrid v1.6.7) |
222649295 | Organization-level UDCA would hang. (Fixed in Apigee hybrid v1.6.7) |
221885751 | Hybrid logging functionality has been reworked. This should resolve issues with excessive log volume generation, frequent logger restarts, and ensure correct logger functionality with both docker and containerd runtimes. (Fixed in Apigee hybrid v1.5.8) |
221292104 | Fix to address failure to capture requests in Debug sessions involving PostClientFlow ServiceCallouts. (Fixed in Apigee X, May 9, 2022) |
221266789 | Hybrid logging functionality has been reworked. This should resolve issues with excessive log volume generation, frequent logger restarts, and ensure correct logger functionality with both docker and containerd runtimes. (Fixed in Apigee hybrid v1.6.7) |
219622478 | Fixed the CPS property token so that when set to true , it will allow the instance to shutdown and reboot when cassandra connection failures occur. (Fixed in Apigee hybrid v1.7.3) |
216018530 | Fixed an issue where the apigee-logger-apigee-telemetry DaemonSet could still be left running after turning off logger. (Fixed in Apigee hybrid v1.7.1) |
213261445 | Fixed reliance on keystore generated by cert manager for metrics endpoint and removed the need for a custom generate_cert script. (Fixed in Apigee hybrid v1.6.7) |
211716827 | Fixed an issue where a non-default gateway could cause routing errors in certain circumstances. (Fixed in Apigee hybrid v1.7.1) |
205616792 | Fixed core dump on running user schema setup. (Fixed in Apigee hybrid v1.7.1) |
202950533 | Remove the server header from all responses. This will be consistent with CG SaaS and OPDK. (Fixed in Apigee hybrid v1.8.0) |
202403896 | Upgrade to Apigee hybrid v1.6 from v1.5 could fail due to annotation size. (Fixed in Apigee hybrid v1.5.8) |
Bug ID | Description |
---|---|
230369447 | Security fix for commons-codec (Fixed in Apigee hybrid v1.8) |
230368838 | Security fix for CVE-2018-10237, auto-value:guava (Fixed in Apigee hybrid v1.8) |
230366823 | Security fix for jackson-databind (Fixed in Apigee hybrid v1.8) |
230366589 | Security fix for CVE-2021-22696-cxf in cxf (Fixed in Apigee hybrid v1.8) |
229804717 | Security fix for CVE-2021-3711 (Fixed in Apigee hybrid v1.8, v1.7, v1.6) |
229804942 | Security fix for CVE-2022-0778 (Fixed in Apigee hybrid v1.8) |
N/A | Miscellaneous Security updates and fixes. |
The apigeectl
--verbose
option has been deprecated. It is replaced with the --v
option which lets you specify the log verbosity level in the format --v=int
, for example apigeectl apply --v=5
. See apigeectl
for details.
August 18, 2022
Apigee ConnectorsSupport for private connectivity through Private Service Connect (PSC)
On August 18, 2022, we released PSC support for hostname configuration in Apigee Connectors.
For all the connectors that require a hostname and port configuration, you can now see a Destinations section when creating the connector. In this section, you must enter the details of the remote host (backend system) you want to connect. You can now specify the destination details either as a host address or a service attachment.
August 15, 2022
Apigee ConnectorsPreview release of new Connectors for Apigee
On August 15, 2022, we released the preview version of the Oracle DB connector for Apigee. For more information, see Create a Oracle DB connection.
August 11, 2022
Apigee XOn August 11, 2022 we released an updated version of Apigee X.
This release contains the new Abuse page in Advanced API Security, which displays information about bots that have been detected by analysis of your API traffic. The Abuse page displays the IP addresses of detected bots, as well as their locations, the bot rules that led to their detection, and other details.
August 10, 2022
Apigee IntegrationOn August 10, 2022 we released an updated version of the Apigee Integration software.
Support for VPC Service Controls (Preview)
VPC Service Controls lets you define a security perimeter around the Apigee Integration Google Cloud service. For more information, see Set up VPC Service Controls for Apigee Integration.
August 03, 2022
Apigee API hubOn August 3, 2022 Apigee hub released a new version of the software.
Bug ID | Description |
---|---|
241241073 | Changed API hub UI route prefix from apigee/api-registry to apigee/hub . The previous apigee/api-registry path will still continue to work, but will redirect to apigee/hub automatically. |
July 29, 2022
Apigee hybridhybrid v1.7.3
On July 29, 2022 we released an updated version of the Apigee hybrid software, v1.7.3.
For information on upgrading, see Upgrading Apigee hybrid to version 1.7.
Bug ID | Description |
---|---|
219622478 | Fixed the CPS property token so that when set to true , it will allow the instance to shutdown and reboot when cassandra connection failures occur. |
238370197 | Fixed an issue where the timeTaken variable's value could sometimes be calculated incorrectly. |
Bug ID | Description |
---|---|
N/A | Security fix for CVE-2022-22963. |
July 27, 2022
Apigee API hubOn July 27, 2022 Apigee hub released a new version of the software.
Bug ID | Description |
---|---|
230374510 | Mitigated issue where specs over 900KB (uncompressed) in size caused timeouts when trying to view their contents, and in turn caused instability with future requests for a short period of time. A warning message is now displayed when attempting to view specs that exceed 900KB. |
230374510 | Fixed issue where viewing spec files that had a file extension of .gz would allow only download of the file and would not display the contents of the file, if supported. |
July 25, 2022
Apigee XOn July 25, 2022, we released an updated version of Apigee X (1-8-0-apigee-23).
Bug ID | Description |
---|---|
N/A | Upgraded infrastructure and libraries |
July 21, 2022
Apigee XOn July 21, 2022 we released an updated version of Apigee X.
The Advanced API Security's target assessment, which evaluates the security of target servers in your API, is now available. See Security scores in the Apigee UI to learn more.
July 19, 2022
Apigee UIOn July 19, 2022 we released an updated version of the Apigee UI.
The Needs Attention Table in Advanced API Security Scores now use links instead of buttons. This fixes font and alignment issues inside the table rows.
Bug ID | Description | 238248377 | The Needs Attention Table in Advanced API Security Scores was not showing target components. This has been fixed. |
---|
July 09, 2022
Apigee IntegrationOn July 09, 2022 we released an updated version of the Apigee Integration software.
Data Mapping task enhancements
The Data Mapping task in Apigee Integrations now provides the following enhancements:
- Nested function support. You can pass one or more transformation functions as input parameters to another function.
New transformation functions. You can use the following new transform functions for array-type variables:
Subfield mapping support for JSON variables. You can view and search all the subfields of a JSON variable in the data mapping editor variable list.
For more information, see the Data Mapping task.
July 08, 2022
Apigee hybridhybrid v1.6.9
On July 8, 2022 we released an updated version of the Apigee hybrid software, v1.6.9.
For information on upgrading, see Upgrading Apigee hybrid to version 1.6.
Bug ID | Description |
---|---|
236129944 | Fixed the controller crashloopbackoff due to null pointer issue. |
234620567 | Fix logger issue in Anthos BareMetal with CentOS. |
231313050 | Fixed issue causing Apigee logger pod to remain in crashloopbackoff state. |
233094108 | Fixed Stacktrace truncation in runtime containers to support proxy diagnosis. |
July 06, 2022
Apigee API hubOn July 6, 2022 Apigee hub released a new version of the software.
Bug ID | Description |
---|---|
229852942 | The error message displayed has been clarified for the case where the uploaded spec file type was not gzip, but the mime type selected was gzip. |
July 01, 2022
Apigee UIOn July 1, 2022, we released an updated version of the Apigee UI.
This release contains a new version of the Debug tab in the Apigee Proxy Editor. Following previous releases of new versions of the Overview and Develop tabs, this completes the initial release of the new Proxy Editor.
To view the new Debug tab, see Using Debug.
June 30, 2022
Apigee ConnectorsPreview release of new Connectors for Apigee
On June 30, 2022 we released the preview version of new connectors for Apigee.
The following new connectors are available for Apigee:
On June 30, 2022 we released an updated version of Apigee X.
This release contains the Public Preview of Advanced API Security, which protects your APIs from unwanted requests, including attacks by malicious clients such as bots, and evaluates the security level of your API configurations.
Advanced API Security lets you:
- Create security reports to detect bots and other threats to your APIs.
- View security scores, which rate the security of your APIs and provide recommendations for improving security.
June 27, 2022
Apigee API hubOn June 27, 2022 Apigee hub released a new version of the software.
Bug ID | Description |
---|---|
227334287 | An improved error dialog is displayed when an error occurs on API delete. |
229852889 | Reference lists now filter out their parent API to prevent self-references. |
232250641 | Resource IDs generated from names are now automatically truncated or padded to conform to length requirements. |
236744313 | Fixed an issue where the spinning progress indicator would not go away. |
June 24, 2022
Apigee hybridhybrid v1.7.2
On June 24, 2022 we released an updated version of the Apigee hybrid software, v1.7.2.
For information on upgrading, see Upgrading Apigee hybrid to version 1.7.
Bug ID | Description |
---|---|
233094108 | Fixed Stacktrace truncation in runtime containers to support proxy diagnosis. |
236129944 | Fixed the controller crashloopbackoff resulting from null pointer. |
231313050 | Fixed issue causing Apigee logger pod to remain in crashloopbackoff state. |
236399482 | Added support for ASM v1.13. |
June 23, 2022
Apigee IntegrationOn June 23, 2022 we released an updated version of the Apigee Integrations software.
Apigee Integration trials
Starting with this release, Apigee Integrations is available in an Apigee Eval org which lets you try out the integrations feature without getting billed for the usage. For information, see Enable integrations in an eval org.
Updates to SetIntegrationRequest policy
The SetIntegrationRequest policy has the following updates:
Support for ref attribute in the <Parameter>, <ParameterArray>, and <Value> elements. By using this attribute, you can assign flow variable values to the parameters.
Empty <Parameter> and <ParameterArray> elements are supported. However, if these elements are empty, Apigee treats the element value as null.
Empty <Value> element is not supported. If the element is empty, Apigee reports an error.
June 21, 2022
Apigee Integrated PortalOn June 21, we released an updated version of Apigee integrated portal.
Added the ability to sort by Name and Created fields in the Apps and Teams tables. Click the column heading to sort.
On June 21, 2022 we released an updated version of the Apigee UI,
The Data Collectors UI is now generally available.
A search bar has been added to the new Proxy Editor Develop view. This lets you search for items within a proxy or sharedflow bundle.
On June 21, 2022, we released an updated version of Apigee X (1-8-0-apigee-18).
Bug ID | Description |
---|---|
234355351 | Fixed issue with message processor pods restarting frequently. Added backoff polling task for Cloud KMS key listener. The listener is paused only when the flush policy is met. |
N/A | Upgraded infrastructure and libraries. |
June 14, 2022
Apigee Integrated PortalOn June 14, we released an updated version of Apigee integrated portal.
Use a GraphQL schema to publish your APIs to an integrated portal.
For details, see:
June 06, 2022
Apigee API hubOn June 6, 2022 Apigee hub released a new version of the software
Bug ID | Description |
---|---|
234772624 | Fixed an issue where an API could not be deleted if it had deployments. |
June 02, 2022
Apigee XOn June 2, 2022, we released an updated version of Apigee X.
Apigee X APIs for managing key value entries in a key value map scoped to an organization, environment, or API proxy are now available. For more information, see the Apigee API reference documentation.
hybrid v1.7.1
On June 2, 2022 we released an updated version of the Apigee hybrid software, v1.7.1.
For information on upgrading, see Upgrading Apigee hybrid to version 1.7.
Bug ID | Description |
---|---|
233349518 | Fixed "Invalid Resource" error generated for job/apigee-resources-install . |
232977937 | Fixed an issue where deployment would become stuck on "Applying routing changes on" for multiple ingress gateways. |
216018530 | Fixed an issue where the apigee-logger-apigee-telemetry DaemonSet could still be left running after turning off logger. |
226964206 | MART, runtime and synchronizer would write to the pod file system. |
211716827 | Fixed an issue where a non-default gateway could cause routing errors in certain circumstances. |
225198475 | Fixed an issue where resource reference changes could not be detected. |
225939342 | Fixed an error where deployment status would show as "Applying routing changes on {env}". |
229824389 | Fixed an issue in hybrid 1.7.0 where the output apigeectl init could be generated in the wrong order. |
229639530 | Fixed an error harmonizing the container process ID to use Apigee ID for Hybrid on OpenShift |
229804717 | Fixed upgrade envoy to use distroless v1.22.0. |
227538469 | Fixed an issue where configuration actions would write logs to the pod file system. |
205616792 | Fixed core dump on running user schema setup. |
225081332 | Fixed allow privileged pods issue. |
May 31, 2022
Apigee UIOn May 31, 2022 we released an updated version of the Apigee UI.
API Monitoring Timeline charts were not displayed correctly in the Timeline view.
Previously, you needed to navigate to another API Monitoring view (such as Investigate) and then return to the Timeline view to see charts. This has been fixed: now you can go directly to the Timeline view to see charts.
hybrid v1.6.8
On May 31, 2022 we released an updated version of the Apigee hybrid software, v1.6.8.
For information on upgrading, see Upgrading Apigee hybrid to version 1.6.
Bug ID | Description |
---|---|
233349518 | Fixed "Invalid Resource" error generated for job/apigee-resources-install . |
225939342 | Fixed an error where deployment status would show as "Applying routing changes on {env}". |
225198475 | Fixed an issue where resource reference changes could not be detected. |
232977937 | Fixed an issue where deployment would become stuck on "Applying routing changes on" for multiple ingress gateways. |
229804717 | Fixed upgrade envoy to use distroless v1.22.0. |
May 25, 2022
Apigee ConnectorsPreview release of new Connectors for Apigee
On May 20, 2022, we released the preview version of the Connectors for Apigee.
The Zendesk connector is available for Apigee. For more information, see Zendesk connection.
You can now create and manage Private Service Connect (PSC) endpoint attachments in the Apigee UI. For details, see Creating an endpoint attachment.
May 23, 2022
Apigee XOn May 23, 2022, we released an updated version of Apigee X (1-8-0-apigee-9).
Bug ID | Description |
---|---|
N/A | Upgraded infrastructure and libraries |
May 18, 2022
Apigee MonetizationOn May 18, 2022 we released an updated version of the Apigee Monetization software.
Apigee X now supports export of additional fee-based values for organizations using monetization. For more information, see Generating monetization reports.
On May 18, 2022, we released an updated version of the Apigee UI.
May 16, 2022
Apigee API hubOn May 16, 2022 Apigee hub released a new version of the software.
Bug ID | Description |
---|---|
232129385 | Users without artifact write permission encountered errors when loading various pages if the default API hub artifacts were not yet initialized by the system. |
May 12, 2022
Apigee ConnectorsPreview release of new Connectors for Apigee
On May 12, 2022, we released the preview version of new Connectors for Apigee.
The following new connectors are available for Apigee:
May 11, 2022
Apigee Integrated PortalOn May 11, 2022 we released an updated version of the Apigee Integrated Portal software.
Bug ID | Description |
---|---|
228603948 | Fixed an issue that prevented users from editing custom fields for account creation and signup. |
228339667 | Documentation now reflects support for the STARTTLS SMTP authorization type. |
227511014 | Fixed an issue that prevented V1 Portals from being upgraded to V2. |
224991572 | Improvements to the Get Started documentation bundled with a new portal. Create a new portal and then click Get Started to see the new content. |
220980189 | Fixed issue with publishing API Products on a Portal when the organization has over 1,000 API Products. |
218320618 | Page descriptions are now limited to 1,000 characters. Page content is now limited to 1 MB. |
210651558 | Fixed issue where adding a new API Product subscription to an App would remove all scopes on the Apps credentials. |
hybrid v1.6.7
On May 11, 2022 we released an updated version of the Apigee hybrid v1.6.7 software.
For information on upgrading, see Upgrading Apigee hybrid to version 1.6.
Bug ID | Description |
---|---|
227600373 | Fixed an installation issue with Cassandra. |
227538469 | Configuration actions would write logs to the pod file system. |
226964206 | MART, runtime and synchronizer would write to the pod file system. |
226464960 | Apigee hybrid fresh installations on OpenShift 4.6 and 4.8 would fail. |
225081332 | Allow privileged pods issue. |
224620542 | On some Kubernetes platforms, logging would fail without adding an empty directory for the logs. |
223081301 | Fixed organization-level UDCA incorrect http-proxy secret name. |
222649295 | Organization-level UDCA would hang. |
221266789 | Hybrid logging functionality has been reworked. This should resolve issues with excessive log volume generation, frequent logger restarts, and ensure correct logger functionality with both docker and containerd runtimes. |
213261445 | Fixed reliance on keystore generated by cert manager for metrics endpoint and removed the need for a custom generate_cert script. |
205616792 | Fixed core dump on running user schema setup. |
May 10, 2022
Apigee hybridhybrid v1.6.7/1.5.10/1.7.0
Known Issue: 231758700 - Apigee Hybrid Dockerhub customers unable to pull images with Docker Content Trust enabled
May 09, 2022
Apigee API hubOn May 9, 2022 Apigee hub released a new version of the software.
Bug ID | Description |
---|---|
231715589 | When viewing the API hub getting started page in the Google Cloud console, if you switched to another un-provisioned project, the browser encountered a redirect loop. |
On May 9, 2022 we released an updated version of the Apigee X software (1-8-0-apigee-5).
The GoogleIDToken.Audience
tag now includes the useTargetUrl
attribute to simplify audience configuration of Google ID tokens for Apigee policies.
Bug ID | Description |
---|---|
221292104 | Fix to address failure to capture requests in Debug sessions involving PostClientFlow ServiceCallouts. |
228855520 | Upgraded ASM to the latest version. |
Bug ID | Description |
---|---|
217497793 | A security issue was addressed. |
May 04, 2022
Apigee API hubOn May 4, 2022 Apigee API hub began the release of a new version of the software for Public Preview.
At Public Preview, products or features are ready for testing by customers. Preview offerings are often publicly announced, but are not necessarily feature-complete, and no SLAs or technical support commitments are provided for these. Unless stated otherwise by Google, Preview offerings are intended for use in test environments only.
Added the API Hub
label in the Apigee community.
Added provisioning instructions.
Documentation: Provision API hub
Added instructions on how to get support.
Documentation: Get support
Action buttons in the UI are now disabled if you do not have appropriate permissions to perform the action.
On May 4, 2022 we released an updated version of the Apigee Integrated Portal software.
Error messages for rejected logins for an inactive user are now more informative to the user.
Emails from portal-sso
will either be the email address of the sender that the user sets up in the custom smtp
settings, or it will be no-reply@google.com
, instead of the human-readable name orgname-portalname
. This screenshot illustrates emails sent from portal-sso
in e2e
. It shows one email with custom smtp
settings (tsnow-custom-smtp
) and one email with the default settings (no-reply
).
Bug ID | Description |
---|---|
220993729 | Portal SSO showed the Apigee domain when hovering over footer links in third-party web pages. |
220188030 | Reset password was not working for LDAP configurations. |
214146121 | An authentication issue with Apigee SSO has been fixed. |
204952689 | Fixed miscellaneous logback error. |
194469693 | Enabled SAML config error so that it is visible. |
194053231 | Added server-side validation for the password field. If the password is non-compliant, the response is 422:Unprocessable Entity . |
190609332 | Improved error output for failures while enabling SSO for Apigee |
157131343 | Added support for the parenthesis () and plus + characters for built-in IDP custom fields. Other special characters will continue to be blocked due to security reasons. |
ID | Description |
---|---|
200604177 | Upgraded jQuery and Bootstrap |
On May 4, 2022 we released an updated version of the Apigee UI.
We have released a new version of the Develop tab in the Proxy Editor. See Introducing the new Proxy Editor.
April 27, 2022
Apigee API hubOn April 27, 2022 Apigee hub released a new version of the software.
All system taxonomy descriptions are now editable.
April 22, 2022
Apigee XOn April 22, 2022 we released an updated version of the Apigee X software (1-7-0-apigee-34).
Bug ID | Description |
---|---|
N/A | Upgraded infrastructure and libraries |
hybrid v1.5.10
On April 22, 2022 we released an updated version of the Apigee hybrid v1.5.10 software.
For information on upgrading, see Upgrading Apigee hybrid to version 1.5.
Bug ID | Description |
---|---|
225169066 | Cassandra database backup and restore was not working when http_proxy is enabled under certain circumstances. |
221885751 | Hybrid logging functionality has been reworked. This should resolve issues with excessive log volume generation, frequent logger restarts, and ensure correct logger functionality with both docker and containerd runtimes. |
202403896 | Upgrade to Apigee hybrid v1.6 from v1.5 could fail due to annotation size. |
221885751 | Multiple issues with the Hybrid logging functionality have been addressed. |
April 20, 2022
Apigee API hubOn April 20, 2022 Apigee hub released a new version of the software.
Changed columns in the History table:
- Changed Date & time to Updated
- Changed Comment to Commit history
- Added ID, which is the ID of the revision as it appears in the registry API.
April 18, 2022
Apigee UIOn April 18, 2022, we released an updated version of the Apigee UI.
The UI for managing Apigee instances has been updated and improved:
- You can now specify a list of accepted Cloud projects that can privately connect to the instance's service attachment.
- The New Instance dialog is replaced by a dedicated Create new instance configuration page with fields for specifying or creating a disk encryption key and for editing the list of accepted projects.
- The Edit instance dialog is replaced by a dedicated page that lets you add or remove environments and edit the list of accepted projects that can privately connect to the instance's service attachment.
- The UI now lets you select the disk encryption key from a list and provides a convenient flow if you want to create a new key.
- The UI for deleting an instance has changed. There is now a DELETE button on the Instance details page.
For more information, see Managing instances.
Bug ID | Description |
---|---|
229008583 | When opening the Apigee UI in multiple tabs with different orgs, some cache entries were not being synched. This has been fixed. |
204429957 | Make ClientSpecificResourceService and ClientResourceNamePipe return plain values. Previously, methods on those classes returned observables. Now they return values. |
Apigee hybrid v1.7.0
On April 18, 2022 we released Apigee hybrid v1.7.0.
For information on upgrading, see Upgrading Apigee hybrid to version 1.7.
mTLS communication between Cassandra clients and Cassandra nodes
Apigee hybrid now supports mTLS communication between Cassandra clients (MART, Sync, and MP) and Cassandra nodes. For related ports used, see feedbackSecure ports usage. (Implemented in Apigee hybrid v1.7.0)
Custom metrics scaling
Apigee hybrid v1.7.0 now supports custom metrics scaling using the metrics:appStackdriverExporter
and metrics:proxyStackdriverExporter
configuration properties. See metrics in the Configuration properties reference. (Implemented in Apigee hybrid v1.7.0)
OAuth JWT access tokens
Apigee hybrid v1.7.0 now supports JWT operations that allow the OAuthV2 policy to generate, verify, and refresh access tokens that conform to the JWT token standard. See Using JWT OAuth tokens. (Implemented in Apigee hybrid v1.7.0)
Cloud Logging
Apigee hybrid v1.7.0 now supports the <CloudLogging>
element in the MessageLogging policy that lets you log messages to Cloud Logging. (Implemented in Apigee hybrid v1.7.0)
PublishMessage policy
Apigee hybrid v1.7.0 now supports the PublishMessage policy that lets you publish your API proxy flow information to a Google Cloud Pub/Sub topic.
Policy document: PublishMessage policy
(Implemented in Apigee hybrid v1.7.0)
GraphQL policy now supports JSON-encoded payloads. (Implemented in Apigee X, March 15, 2022)
Bug ID | Description |
---|---|
224577096 | Support Added for Anthos Service Mesh 1.12 (Fixed in Apigee hybrid v1.6.6) |
219523719 | Fix to address CPU and memory consumption when debug-session is enabled with response-status as the filtering criteria. (Fixed in Apigee X, March 15, 2022) |
217386412 | Change the property set logging level to fine when property is not found. (Fixed in Apigee hybrid v1.6.5) |
215773113 | Setting the securityPolicy appeared to have no effect for specific configurations. (Fixed in Apigee hybrid v1.6.5) |
214960081 | HTTPS endpoints could be called as HTTP resulting in an "EOF unexpected" error. (Fixed in Apigee hybrid v1.6.4) |
211787541 | Errors displayed in synchronizer logs for stale contracts. (Fixed in Apigee hybrid v1.6.5) |
210590135 | Invalid protocol in proxy.url flow variable in Apigee X. The proxy.url flow variable could show as http even when the request is https . (Fixed in Apigee hybrid v1.6.4) |
210314786 | The backup utility did not work with workload identity. (Fixed in Apigee hybrid v1.6.4) |
209622008 | Dynamic updates to rate in spike arrest are now reflected immediately. (Fixed in Apigee X, March 15, 2022) |
209484701 | Invalid client IP sent to analytics. (Fixed in Apigee hybrid v1.6.5) |
209097822 | Fixed and issue where SpikeArrest was not reflecting updated rate (Fixed in Apigee hybrid v1.6.3) |
208474799 | Apigee hybrid now supports ASM version 1.12. See Supported platforms for ASM version support for each supported version of Apigee Hybrid. (Fixed in Apigee hybrid v1.7.0) |
208322185 | Apigee hybrid Cassandra backup and restore can now use either a user-provided custom secret or a generated secret (Fixed in Apigee hybrid v1.6.3) |
207762842 | Hybrid logging functionality has been reworked. This should resolve issues with excessive log volume generation, frequent logger restarts, and ensure correct logger functionality with both docker and containerd runtimes.(Fixed in Apigee hybrid v1.7.0) |
207618262 | Fixed an issue where SpikeArrest opened too many connections to redis-envoy. (Fixed in Apigee hybrid v1.6.3) |
207400645 | Allow direct reads from API server to API client when enabled. (Fixed in Apigee hybrid v1.6.3) |
205820658 | Fixed an issue where Apigee X/hybrid Debug could show the authorization header. (Fixed in Apigee hybrid v1.6.3) |
205810988 | Resolve suspension dialog displayed "user not authorized" message for regions other than US This has been fixed. Location information is now added into the suspension URL from Apigee. (Fixed in Apigee X, December 02,2021) |
205732137 | Handle Quota correctly when the Operation group is set with empty string params (Fixed in Apigee hybrid v1.6.3) |
205148816 | Product Level Quota Info now available in Proxy. (Fixed in Apigee hybrid v1.6.3) |
204943895 | Quota Policy in Shared Flow now working properly. (Fixed in Apigee hybrid v1.6.3) |
204943880 | Fixed issue where SpikeArrest in Shared Flow did not have context of API Proxy. (Fixed in Apigee hybrid v1.6.3) |
204905727 | GenerateResponse was hanging on response flow when enabled=true . (Fixed in Apigee hybrid v1.6.5) |
204368970 | TLS variables are now set by Apigee Runtime. (Fixed in Apigee hybrid v1.6.3) |
204146857 | Fixed an issue where new environments were not created in Apigee hybrid deployment. (Fixed in Apigee hybrid v1.6.3) |
203785814 | A transient error could occur when calling conversion webhook for Apigee Telemetry. The error would occur when Apigee CRD is installed too early in the sequence. The installer job now checks for the correct sequence. (Fixed in Apigee hybrid v1.6.4) |
203468593 | Corrected the storageclass property name. (Fixed in Apigee hybrid v1.5.5) |
203462573 | The StorageClass set in overrides was not honored. (Fixed in Apigee hybrid v1.6.1) |
202560276 | AKS - containerd broke apigee-logger . (Fixed in Apigee hybrid v1.6.1) |
202309278 | Monetization: Eliminated a race condition that could make a prepaid developer's balance appear incorrect. (Fixed in Apigee hybrid v1.6.2) |
202299966 | Added new remote-address-related headers and modified the headers to be RFC compliant. (Fixed in Apigee hybrid v1.6.3) |
200918549 | There was an issue when using forward proxy with the ApigeeConnect agent. (Fixed in Apigee hybrid v1.6.1) |
200700375 | Fixed API products sorting issue in UI. Previously, sorting was disabled on the API products page. Sorting is now enabled. (Fixed in Apigee X, September 23, 2021) |
200648523 | Trace Variable, is_request_blocked, was showing incorrect information. (Fixed in Apigee hybrid v1.6.2) |
199952038 | The apigeectl command uses the new --restore flag to restore Cassandra to a previously saved snapshot. For more information, see Restoring in a single region. (Fixed in Apigee hybrid v1.6.6) |
199807323 | Updating Developer would reset the Developer billing type attribute (Fixed in Apigee hybrid v1.6.2) |
199541025 | Transaction ID is now required to be unique when used with prepaid developer balance credit API. (Fixed in Apigee hybrid v1.6.2) |
198549304, 197730687, 196937143, 188370635, 187890034 | Error state for conflicting dates is now correct. (Fixed in Apigee hybrid v1.6.2) |
198036824 | The securityContext was empty when it should have been populated. (Fixed in Apigee hybrid v1.6.1) |
197945951 | Stale DNS record in MP memory could cause an outage for a proxy. (Fixed in Apigee hybrid v1.6.4) |
197910247 | SetDialogflowResponse Policy - JSONPath expressions were not working. (Fixed in Apigee hybrid v1.6.1) |
197711066 | Cluster upgrade failed due to PDB (PodDisruptionBudget) policy not being met. (Fixed in Apigee hybrid v1.6.1) |
196095557 | Fixed proxy high response times. (Fixed in Apigee hybrid v1.5.4) |
196024622 | Hybrid images contained keys. (Fixed in Apigee hybrid v1.6.1) |
196024483 | Hybrid images did not set USER instruction when building the container. (Fixed in Apigee hybrid v1.6.1) |
193799009 | Fixed wrong status code shown on trace with ServiceCallout in PostClientflow. (Fixed in Apigee hybrid v1.5.4) |
193520269 | Fixed Apigee UI not showing the trace UI. (Fixed in Apigee hybrid v1.5.4) |
193041253 | Cassandra upgraded to v3.11.9 The Cassandra database in Apigee hybrid v1.7.0 has been upgraded to version 3.11.9. (Fixed in Apigee hybrid v1.7.0) |
192987085 | Fixed the ApiProductNotFound exception, which occurred when you deleted an API product but the deletion of associated rate plans was pending. (Fixed in Apigee X Monetization, November 3, 2021) |
191853747 | Apigee Workload Identities not working for specific configurations. (Fixed in Apigee hybrid v1.6.5) |
190679584 | There was an Incorrect error message on deploying AssertCondition policy with invalid condition. (Fixed in Apigee hybrid v1.6.1) |
189341334 | Fixed an issue to eliminate the potential for connection leaks for the watcher component. (Fixed in Apigee hybrid v1.6.3) |
188407113 | Invalid value in the ConsumptionPricingType during rate plan creation displayed the 500 status code. Now the status code for an invalid value is 4xx. (Fixed in Apigee X Monetization, November 3, 2021) |
181259284 | Fixed unresolved flow variables system.region.name and system.pod.name . (Fixed in Apigee hybrid v1.5.4) |
180672249 | FlowCallout succeeded, although SharedFlow had errors in deployment. (Fixed in Apigee hybrid v1.6.1) |
173738907 | Fixed support resource request/limit in override.yaml in apigee-metrics . (Fixed in Apigee hybrid v1.5.4) |
173566787 | Reuse existing target IPs if DNS resolution fail on DNS cache refresh. (Fixed in Apigee hybrid v1.6.5) |
111777025 | LookupCache: cachehit was shown false in trace when the actual value was true. (Fixed in Apigee hybrid v1.6.5)N/A |
N/A | If there is more than one SpikeArrest policy in a bundle, 502 errors will occur. (Fixed in Apigee X, December 12, 2021) |
N/A | If ServiceCallout is "fire and forget" (no tag), a race condition can occur if there is another policy that occurs after it. (Fixed in Apigee X, December 12, 2021) |
N/A | Fix bug delete dialog does not open Previously, on click of delete dialog, the dialog was not appearing, this fixes it (Fixed in Apigee X, October 05, 2021) |
N/A | Dynamic updates to rate in SpikeArrest may not reflect immediately. (Fixed in Apigee X, December 12, 2021) |
Bug ID | Description |
---|---|
217743790 | ** Cassandra backup would run as privileged.** |
204994504 | Container Vulnerability fixed: CVE-2018-12934. (Fixed in Apigee hybrid v1.6.5) |
N/A | Multiple security fixes including CVE-2019-5021. (Fixed in Apigee hybrid v1.6.5) |
N/A | Miscellaneous Security updates and fixes. (Fixed in Apigee X, December 12, 2021) |
205820658 | A security issue was addressed. (Fixed in Apigee hybrid v1.6.2-hotfix.1) |
"Apigee Deployer" role deprecated and replaced by "Apigee Environment Admin" The environment role "Apigee Deployer" has been deprecated, and replaced by "Apigee Environment Admin". (Implemented in Apigee X, December 2, 2022)
April 11, 2022
Apigee ConnectorsPreview release of new Connectors for Apigee
On April 12, 2022, we released the preview version of new Connectors for Apigee.
The following new connectors are available for Apigee:
April 05, 2022
Apigee Integrated PortalOn April 5, 2022 we released an updated version of the Apigee Integrated Portal software.
Bug ID | Description |
---|---|
220377670 | Fixed an issue that prevented users from uploading svg and ico files. |
217600695 | Menus will scroll when they don't fit on the page. |
174476355 | When adding a custom registration field in the accounts-authentication UI for creating/editing a portal, the allowed characters for a custom field has been limited to letters, numbers, and spaces. |
April 04, 2022
Apigee API hubOn April 4, 2022 Apigee hub released a new version of the software.
Delete dialogs will now remain open while the delete operation is being processed.
Bug ID | Description |
---|---|
226195254 | Lifecycle replacements did not take effect on lifecycles that were assigned to versions. |
March 31, 2022
Apigee API hubOn March 31, 2022 Apigee hub released a new version of the software.
Added ability to specify the MIME type of the initial spec file when registering a new API.
Documentation: Register APIs
Added ability to specify the MIME type of the spec file when uploading a new revision.
Documentation: Manage revisions
On March 31, 2022, we released an updated version of Apigee X.
You can now use Private Service Connect (PSC) to connect to Apigee. This architectural pattern eliminates the need to create managed instance groups to forward requests from the global load balancer to Apigee. For details, see Using Private Service Connect.
March 29, 2022
Apigee XOn March 29, 2022, we released an updated version of Apigee X (1-7-0-apigee-28).
Bug ID | Description |
---|---|
N/A | Upgraded infrastructure and libraries |
March 28, 2022
Apigee API hubOn March 28, 2022 Apigee hub released a new version of the software.
Bug ID | Description |
---|---|
226194605 | The design style was not saved on API update. |
226184510 | The related and dependencies edit forms were blank when opened. |
On March 28, 2022 we released an updated version of Apigee X.
You can now use Private Service Connect (PSC) to connect Apigee with backend target services running in VPC networks other than the one that is peered with your Apigee organization. For details, see Southbound networking patterns.
March 24, 2022
Apigee AnalyticsOn March 24, 2022, we released a new version of the Apigee Analytics software.
We welcome your feedback about the anomaly events feature in Advanced API Operations. If you have received an anomaly alert, you can send feedback about the alert in the API Monitoring Investigate dashboard by clicking the Anomaly Feedback button at the top of the Anomaly Event Details pane.
hybrid v1.6.6
On March 24, 2022 we released an updated version of the Apigee hybrid v1.6.6 software.
For information on upgrading, see Upgrading Apigee hybrid to version 1.6.
Bug ID | Description |
---|---|
224577096 | Support Added for Anthos Service Mesh 1.12 |
204368970 | Fixed a bug in TLS variables population |
199952038 | The apigeectl command uses the new --restore flag to restore Cassandra to a previously saved snapshot. For more information, see Restoring in a single region. |
hybrid v1.5.9
On March 24, 2022 we released an updated version of the Apigee hybrid v1.5.9 software.
For information on upgrading, see Upgrading Apigee hybrid to version 1.5.
Bug ID | Description |
---|---|
224577096 | Support Added for Anthos Service Mesh 1.12 |
204368970 | Fixed the bug in TLS variables population |
March 22, 2022
Apigee XOn March 22, 2022, we released an updated version of the Apigee X software.
Support for conditions in IAM policies
You can add resource conditions in your IAM policies. A resource condition lets you have granular control over your Apigee resources. For more information, see Adding resource conditions in IAM policies.
March 17, 2022
Apigee API hubOn March 17, 2022 Apigee API hub released a new version of the software.
Added Related and Dependencies reference list cards to the API detail page.
Added ability to edit the links in the Related and Dependencies reference list cards.
Added title to the APIs list page.
Documentation: Customize the display
Updated the API History table to use the filename as the link to the spec detail page, instead of the timestamp, and swapped the order of the Filename and Date/Time columns.
Documentation: Manage revisions
Changed the label of the "Revision History" tab on the API detail page to "History".
Documentation: Manage revisions
Changed the System icon from a
Lock to a Check and changed the Search filter from a Circled Check to a Check on the Taxonomies page.Documentation: Manage taxonomies
Bug ID | Description |
---|---|
224570429 | Some pages did not set a proper page title. |
223927791 | There was a typo in the API Edit deployment form. |
222122131 | The API Document buttons in the API Deployments table did not update when a version was deleted or updated. |
219989013 | Line breaks did not render in API descriptions. |
218682838 | Could not delete the last revision of a spec if it had artifacts attached. |
210991828 | On the Taxonomy edit form, if an element name generated an ID that was too short or too long, a submit error occurred. |
201782973 | The API Filter form on the APIs list page did not take focus when opened. |
March 15, 2022
Apigee XOn March15, we released version 1.7x of Apigee X (1-7-0-apigee-22).
GraphQL policy now supports JSON-encoded payloads.
KVM pagination support now available (via the API only).
Note: When using the GraphQL policy, you can only provide one graphQL schema for verification in an environment.
Bug ID | Description |
---|---|
209622008 | Dynamic updates to rate in spike arrest are now reflected immediately. |
219523719 | Fix to address CPU and memory consumption when debug-session is enabled with response-status as the filtering criteria. |
March 07, 2022
Apigee API hubOn March 7, 2022 Apigee API hub released a new version of the software.
Added ability to mark a deployment as the recommended deployment for an API.
Added tag to the Deployments table to identify which deployment is currently set as the recommended deployment for the API.
Added a button to the Deployments table that displays the version of the documentation revision that is currently assigned to the deployment and navigates to the documentation view of the revision, when clicked.
Added a button to the APIs list and API detail page that displays the version of the documentation revision that is currently assigned to the recommended deployment and navigates to the documentation view of the revision, when clicked.
Added button to the API detail page that opens the access information panel for the recommended deployment of the API, when clicked.
Changed the "Version" column in the Deployments table to "Documentation".
Added tab for display settings to the Settings page.
Added ability to define an organization name that will be used in the UI to identify APIs owned by the user's organization.
Items in the Deployment selection field in the Get Access side panel now signify if the deployment does not have any access information defined.
Bug ID | Description |
---|---|
221265023 | Fixed issue where the Get Access button in the Deployment list was visible even if the deployment had no access information. |
221265023 | Fixed issue where the Deployment selection field in the Get Access side panel would allow you to select deployments that had no access information defined. |
March 03, 2022
Apigee Adapter for EnvoyEnvoy adapter v2.0.5
On March 3, 2022 we released a new version of Apigee Adapter for Envoy v2.0.5.
Security release to address a Denial of Service (DoS) risk in the prometheus library. See CVE-2022-21698.
On March 3, 2022, we released new features for the Public Preview of configurable API proxies. To learn more, see Introduction to configurable API proxies.
HTTP request transforms are now available for use with configurable API proxies.
With HTTP request transforms, configurable API proxy developers can quickly rewrite HTTP request paths, header, and query parameters using HTTP Request Transforms. Rewriting is enabled using a simple configuration that can reference incoming path template segments, header values, or query parameter values.
For more information, see HTTP request transforms for configurable proxies.
Google authentication for securing targets is now supported when using configurable API proxies.
With this feature, configurable API proxy developers can secure their Google backend services using Google OAuth and automatically grant access to authorized API consumers. This offers the advantage of seamless integration with other Google services, without requiring API producers to manage private keys.
For more information, see Securing targets for configurable proxies.
Southbound mTLS can be enabled for use with configurable API proxies .
By adding south bound mTLS functionality to configurable proxies, Apigee customers can seamlessly maintain their current usage of mTLS when transitioning to the use of configurable proxies, or increase security for communications between existing configurable proxies and their backends.
For more information, see Enable south bound mTLS for configurable proxies.
Configurable API proxies now support the use of template variables.
Apigee property sets can be used to specify template variables for configurable API proxies in archive deployments. This feature enables customers to use string templates in their proxy configuration YAML files.
For more information, see Template variables for configurable proxies.
March 01, 2022
Apigee hybridhybrid v1.5.8
On March 1, 2022 we released an updated version of the Apigee hybrid v1.5.8 software.
For information on upgrading, see Upgrading Apigee hybrid to version 1.5.
Bug ID | Description |
---|---|
219523719 | Fix to address the CPU and memory consumption when debug-session is enabled with response-status as the filtering criteria. |
217386412 | Change the property set logging level to fine when property is not found. |
215773113 | Setting the securityPolicy appeared to have no effect for specific configurations. |
209484701 | Invalid client IP sent to analytics. |
189233354 | Distributed tracing with Jaeger would error out. |
Bug ID | Description |
---|---|
N/A | Multiple security fixes including CVE-2019-5021. |
February 28, 2022
Apigee hybridhybrid v1.6.5
On February 28, 2022 we released an updated version of the Apigee hybrid v1.6.5 software.
For information on upgrading, see Upgrading Apigee hybrid to version 1.6.
Bug ID | Description |
---|---|
217386412 | Change the property set logging level to fine when property is not found. |
215773113 | Setting the securityPolicy appeared to have no effect for specific configurations. |
211787541 | Errors displayed in synchronizer logs for stale contracts. |
209484701 | Invalid client IP sent to analytics. |
204905727 | GenerateResponse was hanging on response flow when enabled=true . |
191853747 | Apigee Workload Identities not working for specific configurations. |
173566787 | Reuse existing target IPs if DNS resolution fail on DNS cache refresh. |
111777025 | LookupCache: cachehit was shown false in trace when the actual value was true. |
Bug ID | Description |
---|---|
217743790 | ** Cassandra backup would run as privileged.** |
204994504 | Container Vulnerability fixed: CVE-2018-12934. |
N/A | Multiple security fixes including CVE-2019-5021. |
February 24, 2022
Apigee Integrated PortalOn February 24, 2022 we released an updated version of the Apigee Integrated Portal software.
Bug ID | Description |
---|---|
216299743 | Inconsistent button icon for delete in Pages. Updated the page delete button from | (circle with x) to (trash can).
210539825 | CSS compiler should gracefully handle errors with unexpected form. Fixed a rare issue where some custom CSS payloads would result in an Internal Server Error . |
205579028 | 500s caused by could not get auth token for GCP . Periodically, under high load, GCP Authentication would fail on the backend and return a 500 internal exception . |
194226935 | Update site pages to link to Quickstart documentation. The Quick Start tutorial is no longer embedded in the portal. See Build your first portal in the Apigee documentation. |
February 22, 2022
Apigee UIOn February 22, 2022 we released an updated version of the Apigee UI software.
The following accessibility improvements have been made in the Apigee UI:
- In the Develop > API Proxies view, the screen reader now reads "Create new proxy" for the Create New button
- In the Traffic column of the API Proxies view, the screen reader now reads the traffic tooltip text, and the tooltip has been removed.
- In the Last Modified column, the screen reader now reads a message like "5 months ago on Sep 17, 2021 6:21 PM," and the tooltip has been removed.
- Hovering the mouse in the Action column now displays a menu showing the Delete item, to make it accessible.
Bug ID | Description |
---|---|
170748813 | The help text in the project selector menu at the top of the UI was out of date. The information has now been updated. |
220188457 | Proxy/sharedflow undeployment was failing in the new Proxy Editor. This has been fixed. |
February 21, 2022
Apigee IntegrationOn February 21, 2022 we released an updated version of the Apigee Integration software.
Bug ID | Description |
---|---|
N/A | Cloud Pub/Sub trigger having same topic in multiple region fails. You can now create a Cloud Pub/Sub trigger for the same topic in multiple regions. Because of this fix, your already existing Cloud Pub/Sub trigger may now execute multiple times. Contact Apigee support if you notice this problem. However, if you haven't used the Cloud Pub/Sub trigger in your integrations, you can ignore this fix. |
February 15, 2022
Apigee API hubOn February 15, 2022 Apigee API hub released a new version of the software.
Added Deployment List to API detail page.
Documentation: Deployments and Manage deployments
Added ability to create new deployments for an API.
Added ability to edit existing deployments for an API.
Added ability to delete existing deployments for an API.
Added ability to view access information for a deployment of an API.
On February 15, 2022 we released an updated version of the Apigee UI software.
New Overview Tab in Proxy Editor
We have released a new version of the Overview tab in the Proxy Editor. See Introducing the new Proxy Editor.
Note: The new features in this release will be rolled out over the next week, so you might not be able to view them until the rollout is complete.
The UI now shows a warning when an API Product is in legacy format, stating that some of the displayed fields might be legacy fields.
Bug ID | Description |
---|---|
201759530 | Operations that did not have methods defined were not appearing in the operations table in the API Products UI |
199814779 | The test button in Admin > Environments > Keystores was not working correctly. The button has been temporarily removed from the UI. |
On February 15, 2022 we released an updated version of the Apigee X software.
Backend target routing with Private Service Connect
You can now use Private Service Connect (PSC) to connect Apigee with backend target services running in VPC networks other than the one that is peered with your Apigee organization. For details, see Southbound networking patterns.
February 09, 2022
Apigee API hubOn February 9, 2022 Apigee API hub released a new version of the software.
Changed "Add API" to "Register API" across the application.
API search now matches description text.
Bug ID | Description |
---|---|
216809912 | Gateway taxonomy has been removed from the API edit form. |
218092962 | The filter button did not close the API filter. |
February 08, 2022
Apigee Integrated PortalOn February 8, 2022 we released an updated version of the Apigee Integrated Portal software.
Bug ID | Description |
---|---|
212421254 | Consumers can access teams in a portal for which they have no IDP account. Before, a consumer could access a team as long as they were added to the team and had an IDP account in the same organization as the team. Now they can only access the team if they are added as a member and have an IDP account in the same portal as the team. |
209436418 | Display asset file sizes in megabytes. Asset file size was being incorrectly displayed in mebibytes and is now shown in megabytes. |
207130598 | Improve asset upload error messages. Improved an error message when an unsupported image type was uploaded. |
205963075 | New portal name rules are not enforced on backend. The same portal name rules that were already enforced on the front end are now also enforced on the backend. |
205881764 | Cannot delete mobile logo/favicon in Apigee X/Hybrid. Fixed a bug where Apigee X and Hybrid customers could not delete mobile logos or favicons. |
205629978 | Broken HTML after portals v2 migration. The live portal of the upgraded portal will not be displayed correctly after migrating a portal from v1 to v2. |
205581372 | Users endpoint should not crash when passed an invalid Enum value. Passing an invalid sortBy value to the providers/{scope}/users endpoint is now handled gracefully. |
196875216 | Team does not exist exceptions should not be reported as 500s . When API producers attempted to retrieve a team which does not exist, they got an uniformative 500 . Now they get an easy-to-read 404 . |
On February 8, 2022 we released an updated version of the Apigee UI software.
Bug ID | Description |
---|---|
212782769 | An issue prevented editing a new target server that used a keystore reference, and selecting a key alias when using a keystore. |
On February 8, 2022 we released an updated version of the Apigee X software.
Bug ID | Description |
---|---|
N/A | Upgraded infrastructure and libraries |
February 02, 2022
Apigee UIOn February 2, 2022 we released an updated version of the Apigee UI software.
The Apigee provisioning wizard can now auto-allocate /22 and /28 IP address ranges, instead of the larger /21 range
This feature makes it easier to allocate IP address ranges when you are provisioning Apigee. The feature is an enhancement to the IP range feature released on Jan. 24, 2022.
Bug ID | Description |
---|---|
205810610 | Products couldn't be removed from an app if the product's name contained a trailing space |
January 31, 2022
Apigee API hubOn January 31, 2022 Apigee API hub released a new version of the software.
Bug ID | Description |
---|---|
216513294 | API hub pages did not refresh after switching projects. |
hybrid v1.6.4
On January 31, 2022 we released an updated version of the Apigee hybrid v1.6.4 software
For information on upgrading, see Upgrading Apigee hybrid to version 1.6.
Bug ID | Description |
---|---|
214960081 | HTTPS endpoints could be called as HTTP resulting in an "EOF unexpected" error. |
210590135 | Invalid protocol in proxy.url flow variable in Apigee X. The proxy.url flow variable could show as http even when the request is https . |
203785814 | A transient error could occur when calling conversion webhook for Apigee Telemetry. The error would occur when Apigee CRD is installed too early in the sequence. The installer job now checks for the correct sequence. |
197945951 | Stale DNS record in MP memory could cause an outage for a proxy. |
210314786 | The backup utility did not work with workload identity. |
January 28, 2022
Apigee XOn January 28, 2022 we released an updated version of the Apigee X software.
UI updates for service networking and instance creation
UI updates were made to support changes to network IP CIDR range requirements for service networking and instance creation. These changes simplify Apigee provisioning.
hybrid v1.5.7
On January 28, 2022 we released an updated version of the Apigee hybrid v1.5.7 software
For information on upgrading, see Upgrading Apigee hybrid to version 1.5.
Bug ID | Description |
---|---|
214960081 | HTTPS endpoints could be called as HTTP resulting in an EOF unexpected error. |
204368970 | TLS variables were not being set by Apigee Runtime. |
189341334 | Fixed potential connection leaks for watcher component. |
January 26, 2022
Apigee API hubOn January 26, 2022 Apigee API hub released a new version of the software.
Added the ability to view the contents of spec revisions.
Added the ability to download spec revision files.
January 24, 2022
Apigee XOn January 24, 2022 we released an updated version of the Apigee X software.
Reduce the IP range required to peer your VPC network
The required IP range needed to peer your VPC network to the Apigee network is now limited to a non-overlapping CIDR range of /22. This change simplifies Apigee provisioning. Note that the provisioning step for service network configuration has been updated to reflect this change. For more information, see Understanding peering ranges.
January 21, 2022
Apigee API hubOn January 21, 2022 Apigee API hub released a new version of the software.
Added API spec Revision history tab to the API detail page.
Added the ability to upload new API spec revisions from the API spec Revision history tab.
Added the ability to add new versions from the API spec Revision history tab.
January 19, 2022
Apigee IntegrationOn January 19, 2022 we released an updated version of the Apigee Integration software.
Filter clause in the Connectors task
You can add a filter to restrict the amount of data processed by an entity operation. For more information, see Add a filter for an operation.
Upload and download integrations
The Upload/download menu button in the integration designer lets you upload and download integrations in a JSON file format. For more information, see Upload and download integrations.
January 17, 2022
Apigee UIOn January 17, 2022 we released an updated version of the Apigee UI software.
Bug ID | Description |
---|---|
211983110 | Product link in app detail page was broken. |
December 15, 2021
Apigee API hubOn December 15, 2021, Apigee API hub launched as private preview.
Private preview is available by invitation to a small set of customers for testing and feedback before becoming more broadly available.
At private preview, products or features are ready for testing by customers. Preview offerings are often publicly announced, but are not necessarily feature-complete, and no SLAs or technical support commitments are provided for these. Unless stated otherwise by Google, private preview offerings are intended for use in test environments only.
December 03, 2021
Apigee Adapter for Envoyv2.0.4
On December 3, 2021 we released an updated version of the Apigee Adapter for Envoy v2.0.4 software.
▶ Click to see the list of supported platforms.
We publish binaries for MacOS, Linux, and Windows, and in this version, we support the following platforms:
- Apigee hybrid version 1.4.x, 1.5.x, 1.6.x
- Apigee X
- Apigee Edge for Public Cloud
- Apigee Edge for Private Cloud
- Istio versions 1.10, 1.11, 1.12
Envoy versions 1.17, 1.18, 1.19, 1.20
Bug ID | Description |
---|---|
360 | A nil-check was added for the PEM block private key loading to avoid panic. |
104 | Remote service authorization errors are now logged at the Debug level. An exception to this categorization is made for token fetching errors for API keys. In that case, errors are logged at the Error level so that they are visible even if Debug log level for apigee-remote-service-envoy is disabled. See also Setting remote service log levels. |
The list of supported Envoy and Istio versions for the CLI samples command has been updated. These versions are now supported for samples:
- Envoy versions 1.18 to 1.20
- Istio versions 1.10 to 1.12
November 03, 2021
Apigee MonetizationOn November 3, 2021 we released an updated version of the Apigee Monetization software.
DataCapture policy captures monetization variables
You can configure the DataCapture policy to capture a transaction's monetization information such as revenue, currency, price multiplier, and status. For more information, see Monetization variables.
Prepaid billing
Apigee now supports the prepaid billing of developers, as well as postpaid billing. In prepaid billing, app developers pay in advance even before using your API products. The upfront payment made by the developers is available in the developer's wallet, which can have different currencies. You can track a developer's balance in real time and block API calls if a developer has insufficient funds.
Revenue sharing with developers
The revenue sharing feature enables developers to receive a percentage of the total revenue generated. As an API provider, you can configure Revenue share in your rate plan to share a specific percentage of the revenue with your developer partners.
Volume banded consumption pricing
Rate plan supports the new Banded type of consumption based fees. You can configure variable fees for each monetized transaction based on a band. A band refers to an API consumption range, and you can configure a different fee for each band.
Dynamic consumption pricing
To calculate the cost of a transaction, you can specify a multiplier (perUnitPriceMultiplier) value on top of the pre-configured base price in your DataCapture policy.
Criteria for successful transaction
You can specify if a transaction must be monetized or not by configuring the transactionSuccess monetization variable in your DataCapture policy.
Bug ID | Description |
---|---|
199807323 | A prepaid developer is set as a postpaid developer after updates to the prepaid developer. |
198549304, 197730687, 196937143, 188370635, 187890034 | Apigee displays improved error messages during rate plan creation. |
192987085 | Fixed the ApiProductNotFound exception, which occurred when you deleted an API product but the deletion of associated rate plans was pending. |
188407113 | Invalid value in the ConsumptionPricingType during rate plan creation displayed the 500 status code. Now the status code for an invalid value is 4xx . |
The rateplans
API doesn't support the paymentFundingModel
field.
October 06, 2021
Apigee ConnectorsGA release
On October 6, 2021 we released the GA version of the Apigee Connectors software.
Support for display names in the Connectors UI
Connectors now supports the addition of a display name for connections in the Connectors UI.
Service Account authentication for Connection workloads
With this release, Connectors now supports the use of customer Service Accounts as an authentication option for most Connectors workloads.
Support for pagination in LIST calls to Entity APIs
Connectors now supports the option to paginate LIST calls to Entity APIs from Apigee Integration. With the pagination option, Apigee Integration can now request lists of entities in batches using the Connector task.
September 21, 2021
Apigee Adapter for Envoyv2.0.3
On September 21, 2021 we released an updated version of the Apigee Adapter for Envoy v2.0.3 software.
▶ Click to see the list of supported platforms.
We publish binaries for MacOS, Linux, and Windows, and in this version, we support the following platforms:
- Apigee hybrid version 1.4.x, 1.5.x, 1.6.x
- Apigee X
- Apigee Edge for Public Cloud
- Apigee Edge for Private Cloud
- Istio versions 1.10, 1.11, 1.12
Envoy versions 1.17, 1.18, 1.19
Bug ID | Description |
---|---|
N/A | An analytics logging issue with direct responses was fixed. The issue only occurred under certain circumstances. For example: a) For requests not requiring authn/z check, no authContext was generated and dynamic metadata was nil causing the access log entry to be ignored. b) The denied response used RPC code instead of HTTP code, causing records to be shown in the Apigee UI as success. |
September 08, 2021
Apigee ConnectorsPrivate preview release
This is a Private preview of the Connectors feature for Apigee Integration on Apigee X. With the release of Connectors, Apigee Integration customers can connect to business applications, technologies, and other data sources using the native protocols of each target application. With Connectors, both Google Cloud services and third-party business applications are exposed to Apigee Integration through a transparent, standard interface. Apigee Integration users can quickly connect to a growing pool of applications and systems of record without the need for protocol-specific knowledge or the use of custom code.
With this release, the Connectors platform is now available within the Cloud console under Apigee > Connectors. Users with Apigee credentials, Apigee X orgs, and Connectors entitlement can use the Connectors UI to create new connections for use in Apigee Integration.
Connectors supported in this release:
- BigQuery (Preview) connection
- Salesforce connection
- CloudSQL for MySQL connection
- CloudSQL for PostgreSQL connection
- Cloud Pub/Sub connection
Learn more:
August 09, 2021
API GatewayReleased a Preview version of HTTP(S) Load balancing for API Gateway.
The integration of Google Cloud HTTP(S) Load Balancing support for API Gateway enables your serverless backends to take advantage of all the features provided by Cloud Load Balancing. By combining API Gateway and HTTP(S) Load Balancing using a serverless Network Endpoint Group (serverless NEG), you can:
- Host gateways with custom branded domains
- Configure TLS for gateways using certificates issued by a preferred certificate authority
- Create a common entry point for a gateway routing to multiple backends
- Deploy gateways in multiple geographic regions for high availability without managing URLs for each region
To provide feedback or to log issues with this release, see Getting support.
March 24, 2021
Apigee AnalyticsOn March 24, 2021 we released an updated version of the Apigee Analytics software.
Advanced API Operations
This is the GA release of Apigee's Advanced API Operations (AAPI Ops), which provides tools to help you ensure that your APIs stay up and running as intended. AAPI Ops automatically detects unusual patterns in API traffic—called anomalies—such as spikes in latency or error rate.
AAPI Ops enables you to:
February 05, 2021
Apigee AnalyticsOn February 5, 2021 we released an updated version of the Apigee Analytics software.
Recent view
The new API Monitoring Recent view displays treemaps of API traffic by proxy. A treemap displays traffic data for each proxy as a rectangle, whose size is proportional to the amount of traffic in the proxy. The colors of the rectangle indicate the relative sizes of the following variables:
- Number of incidents triggered by alerts.
- Error rate
- Maximum latency 50th percentile (median)
Additional channels for sending alert notifications
Apigee API Monitoring now supports the following channels for sending alert notifications:
- PagerDuty
- Slack
- Webhooks
January 21, 2021
API GatewayReleased a GA version of API Gateway.
To provide feedback or to log issues with this release, see Getting support.
An updated REST API reference for the v1
version is available.
API Gateway is added to the gcloud command group. Users should upgrade to the latest gcloud
release to access the API Gateway command group.
gRPC support is available for Cloud Run backend services. For more information, see Getting started with API Gateway and Cloud Run for gRPC.
API Gateway support for the us-east1
region is now available.
September 08, 2020
API GatewayReleased a beta version of API Gateway.
To provide feedback or to log issues with this release, see Getting support.
Newly created gateways have an updated default hostname pattern:
https://GATEWAY_ID-HASH.REGION_CODE.gateway.dev
where GATEWAY_ID is the name of the gateway, HASH is the unique hash code generated when you deployed the gateway, and REGION_CODE is the code for the Google Cloud region where the gateway is deployed.
For more information, see Deploying an API to a gateway.
The API Gateway API is now publicly visible. Allowlisting is no longer required to view or enable the API in your Google Cloud project.
Deprecated fields are no longer present in alpha versions of the API and the API Gateway UI utilizes the beta API.
API Gateway is added to the gcloud beta
command group. Alpha users and trusted testers should upgrade to the latest gcloud
release to access the API Gateway beta command group.
An updated REST API reference for the v1beta
version is available.
Projects with gateways created between July 14, 2020 and August 6, 2020 may encounter an issue when new gateways are created with the beta API. The *gateway.dev
hostname of the new gateway may return a 404
error response. A resolution to this issue is in progress. In the meantime, we recommend creating or using a new Google Cloud project when using the beta API.
Gateways created during alpha with *.run.app
hostnames (created prior to July 14, 2020) will be turned down shortly after the beta release. We recommend creating new gateways using the v1beta
API. Gateways created with the beta API will have *.gateway.dev
hostnames.
API configs created prior to June 2, 2020 can no longer be deployed to gateways. These configs will be deleted through an internal process.
API Gateway built-in IAM roles are not initially visible. As a result, management permissions are not displayed on the permissions panel within the API Gateway UI. However, permissions to manage API Gateway resources can be granted as expected via Project Owner, Editor, and Viewer roles. A resolution to this issue is in progress.
API Gateway does not support custom IAM roles. A resolution to this issue is in progress.
When creating an API config, and in particular the first config for a new service, the operation may take several minutes to complete as the config is propagated to downstream systems. Creation of a complex API config could take up to ten minutes to complete successfully.
July 01, 2020
API GatewayReleased an updated version of the Alpha version of API Gateway.
To provide feedback or to log issues with this release, see Getting support.
Newly created gateways now have an updated default hostname pattern:
https://GATEWAY_ID-HASH.REGION_CODE.gateway.dev
where GATEWAY_ID is the name of the gateway, HASH is the unique hash code generated when you deployed the gateway, and REGION_CODE is the code for the Google Cloud region where the gateway is deployed.
For more information, see Deploying an API to a gateway.
OpenAPI specifications for API configs no longer require the host
property. You can either omit the host
property entirely or set it to the DNS name of the deployed API. API providers often set it to the DNS name when sharing the OpenAPI Spec with their API consumers. However, the value of the host
property is not enforced by API Gateway. Do not set the host
property to null or an empty value, as this will result in an error.
For more information, see OpenAPI overview.
Updated the REST API reference to the latest Alpha version.
When creating an API config, and in particular the first config for a new service, the operation may take several minutes to complete as the config is propagated to downstream systems. Creation of a complex API config could take up to ten minutes to complete successfully.
When creating a gateway, permissions can take more than a minute to propagate through the system. Therefore, you might see a "missing tokens" error when making a request to an API. If you see this error, wait several minutes, then retry the request.
April 01, 2020
API GatewayAlpha update release of API Gateway
Released an updated version of the Alpha version of API Gateway.
To provide feedback or to log issues with this release, see Getting support.
You can now use the Google Cloud Console UI, a web-based, graphical user interface, to develop your APIs. See the Quickstart: Use the UI to deploy an API on API Gateway for more.
The gcloud
command-line tool now supports new command options, including:
Create, list, update, and delete APIs. That means you no longer have to use Cloud Endpoints commands to work with an API. See Creating an API for more.
Update an API config to modify its labels or display name. See Updating an API config for more.
Updated the REST API reference to the latest Alpha version.
Previously, when the gcloud
command failed while creating an API config, the API config was still created, requiring you to manually delete it. The gcloud
command no longer requires you to delete the API config when the create command fails.
When creating a gateway, permissions can take more than a minute to propagate through the system. Therefore, you might see a "missing tokens" error when making a request to an API. If you see this error, wait several minutes, then retry the request.
Authentication is only supported for Cloud Run and Cloud Functions, not for App Engine.
March 01, 2020
API GatewayReleased the Alpha version of API Gateway.
To provide feedback or to log issues with this release, see Getting support.
When creating a gateway, permissions can take more than a minute to propagate through the system. Therefore, you might see a "missing tokens" error when making a request to an API. If you see this error, wait several minutes, then retry the request.
Authentication is only supported for Cloud Run and Cloud Functions, not for App Engine.