Apigee

1.36.0 — 3^rd July

Update

Add JavaScript Callout Policy Export Option for Blocking

Apigee Agent now supports exporting blocking policies using the JavaScript Callout policy. This allows greater flexibility for customizing blocking behavior within Apigee by leveraging JavaScript logic in policy execution. For more information, see the Apigee Blocking Policy topic.

1.35.0 — 19^th February

Traceable’s Apigee agent’s 1.35.0 release provides the following:

Update

Support for Multiple Environments in the Same TPA

The Apigee agent now supports specifying an environment as part of the Apigee configuration. This allows multiple environments to be managed within the same Traceable Platform Agent (TPA) deployment.

• New Configuration Variable: ta_environment_name

1.34.0 — 28^th February

Traceable’s Apigee agent’s 1.34.0 release provides the following:

Update

Added support for custom blocking messages, status codes, and response headers from the Traceable Platform Agent (TPA). This allows for more customizable responses when API requests are blocked.

1.33.0 — 17^th January

Traceable’s Apigee agent’s 1.33.0 provides the following:

Update

• Dynamically Configure Traceable Policy Using Context Variables
  This release introduces the ability to configure the Traceable policy in Apigee using dynamic context variables. Users can now specify context variable names in the configuration, enabling the policy to fetch and use values dynamically at runtime.
  Example Usage:

  To dynamically set the service name, configure the ta_service_name_var property to reference a context variable:

  <Property name="ta_service_name_var">api.name</Property>

  In this example, the service name is dynamically set to the value of the api.name context variable.