VPC Service Controls (VPC-SC) integration (Preview) API hub now integrates with VPC Service Controls, providing enhanced network security for your API hub instance provisioned in Google Cloud

## Feature **VPC Service Controls (VPC-SC) integration** ([Preview](https://cloud.google.com/products#product-launch-stages)) API hub now integrates with VPC Service Controls, providing enhanced network security for your API hub instance provisioned in Google Cloud. Establish service perimeters to control ingress and egress traffic. For more information, see [VPC Service Controls for API hub](https://cloud.google.com/apigee/docs/apihub/vpc-service-control). ## Feature **Data Residency Zone (DRZ) compliance** API hub is now compliant with Data Residency Zone (DRZ) C3 requirements. For more information, see [API hub locations](https://cloud.google.com/apigee/docs/apihub/locations). ## Feature **Terraform support for provisioning** You can now provision API hub instances programmatically using Terraform for Google Cloud within Cloud Shell, enabling infrastructure-as-code practices. For more information, see [Provision API hub using Terraform](https://cloud.google.com/apigee/docs/apihub/provision-terraform). ## Feature **Plugin Framework** API hub now uses a plugin framework to connect and ingest API metadata from various Google Cloud services and external sources where your APIs are managed or defined. This provides a flexible and extensible way to integrate with your existing API landscape. For more information, see [Plugins overview](https://cloud.google.com/apigee/docs/apihub/plugins). ## Feature **API Metadata Curations** API hub introduces a curation process to transform and enrich API metadata ingested by plugins. This ensures consistency across different sources, enabling effective governance, discovery, and management of your APIs. For more information, see [Curations overview](https://cloud.google.com/apigee/docs/apihub/curations). ## Feature **API Supply chain graph view** Visualize and understand the dependencies within your API ecosystem with the new interactive API supply chain graph view. This directed graph allows you to explore the relationships between your APIs and API operations. For more information, see [API Supply chain views](https://cloud.google.com/apigee/docs/apihub/api-supply-chain#api-supply-chain-views). ## Feature **Enhancements to the Operations entity \[API only\]** You can now add, edit, or delete operations for an API version even if it lacks a specification file or has an unparsable one. For more information, see [Manage operations](https://cloud.google.com/apigee/docs/apihub/manage-operations). ## Change **Attach API documents** You can now enhance your API documentation by attaching additional relevant files, such as requirements, design documents, and functionality details, directly to your APIs in API hub. ## Feature **Deprovision an API hub instance \[API only\]** You can now delete an API hub instance from your Google Cloud project using the [ApiHubInstance](https://cloud.google.com/apigee/docs/reference/apis/apihub/rest/v1/projects.locations.apiHubInstances) API. For more information, see [Deprovision Apigee API hub](https://cloud.google.com/apigee/docs/apihub/deprovision). ## Feature **Build Conversational Agents with Dialogflow CX** ([Preview](https://cloud.google.com/products#product-launch-stages)) Application Integration now simplifies the creation of conversational experiences with direct integration with Conversational Agents (Dialogflow CX). Using API triggers, you can now build intelligent chatbots and automated tools directly within your integration workflows, enhancing user interactions and automating tasks. For more information, see [Build conversational agents with Application Integration](https://cloud.google.com/application-integration/docs/conversational-agents). ## Change **Enhancements to Replay Execution** Application Integration Replay Execution now provides the following enhancements: * **Modify input parameters on replay:** You can now modify the input parameters of an integration execution when initiating a replay. This provides greater flexibility in fixing failed executions. * **Continue execution from point of failure:** When replaying an integration, you can now choose to continue the execution from the point of the last failure. This will retry the failed task and, upon success, continue the execution from that point, saving time and effort. For more information, see [Introduction to replay executions](https://cloud.google.com/application-integration/docs/replay-executions).