Combina criteri e risorse in un flusso condiviso che puoi utilizzare da più proxy API e persino da altri flussi condivisi. Sebbene sia simile a un proxy, un flusso condiviso non ha un endpoint. Può essere utilizzato solo da un proxy API o da un flusso condiviso che si trova nella stessa organizzazione del flusso condiviso stesso.
Per creare un flusso condiviso utilizzando Apigee in Cloud Code:
Esegui uno dei seguenti passaggi:
Posiziona il cursore sulla cartella sharedflows nel tuo spazio di lavoro locale e fai clic su .
Seleziona Visualizza > Tavolozza comandi per aprire la tavolozza dei comandi e seleziona Cloud Code: Create Apigee shared flow bundle.
Si apre la procedura guidata Crea flusso condiviso.
Inserisci un nome univoco per il flusso condiviso al prompt e premi Invio.
Dopo aver completato i passaggi della procedura guidata, il nuovo nome del flusso condiviso viene visualizzato
in sharedflows nella sezione Apigee. Ogni cartella di flussi condivisi è strutturata come descritto in Struttura delle directory del bundle di flussi condivisi.
Caricamento di un bundle di flussi condivisi
Per caricare un bundle di flussi condivisi utilizzando Apigee in Cloud Code:
Esegui una delle seguenti azioni:
Nell'area di lavoro locale, posiziona il cursore sulla cartella sharedflows e fai clic su .
Seleziona Visualizza > Tavolozza comandi per aprire la tavolozza dei comandi e seleziona Cloud Code: Importa bundle di flussi condivisi Apigee.
(Facoltativo) Per impostazione predefinita, il nome del file ZIP meno l'estensione viene utilizzato per il nome del flusso condiviso. Se questo nome non è univoco, ti viene chiesto di inserirne uno univoco.
La cartella del flusso condiviso caricata viene aggiunta in sharedflows nel tuo workspace Apigee.
Configurazione dei flussi condivisi
Configura i flussi condivisi come descritto nei seguenti argomenti:
Puoi chiamare un flusso condiviso utilizzando il criterio FlowCallout, come descritto in Criterio FlowCallout.
Inoltre, collegando un flusso condiviso a un hook di flusso, puoi eseguire il flusso condiviso prima di una richiesta proxy o di destinazione oppure dopo una risposta proxy o di destinazione. Per ulteriori informazioni, vedi:
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-05 UTC."],[[["\u003cp\u003eThis page covers creating and managing shared flows in Apigee and Apigee hybrid, which are reusable sequences of policies and resources.\u003c/p\u003e\n"],["\u003cp\u003eShared flows are similar to API proxies but lack endpoints, and they are called from API proxies or other shared flows within the same organization.\u003c/p\u003e\n"],["\u003cp\u003eYou can create a new shared flow using Apigee in Cloud Code by using a wizard or command, which involves specifying a unique name.\u003c/p\u003e\n"],["\u003cp\u003eShared flow bundles can be imported into Apigee in Cloud Code, and you can configure shared flows by creating reusable ones, adding policies and managing resources.\u003c/p\u003e\n"],["\u003cp\u003eShared flows can be called via the FlowCallout policy or by attaching them to flow hooks, allowing execution before or after proxy or target requests/responses, but runtime dependency validation is necessary.\u003c/p\u003e\n"]]],[],null,["# Developing shared flows\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\n\u003cbr /\u003e\n\nCombine policies and resources into a shared flow that you can consume from multiple API proxies, and even from other shared flows. Although it's like a proxy, a shared flow has no endpoint. It can be used only from an API proxy or shared flow that's in the same organization as the shared flow itself.\n\nDevelop your shared flows using Apigee in Cloud Code as described in the following sections. See also [Managing folders and files in an Apigee workspace](/apigee/docs/api-platform/local-development/vscode/manage-apigee-workspace#manage-folders-files).\n| **Before you begin** : Familiarize yourself with the concepts described in the following topics:\n|\n| - [Creating reusable shared flows](/apigee/docs/api-platform/fundamentals/shared-flows)\n| - [Attaching a shared flow using a flow hook](/apigee/docs/api-platform/fundamentals/flow-hooks)\n\nCreating a shared flow\n----------------------\n\nTo create a shared flow using Apigee in Cloud Code:\n\n1. Perform one of the following steps:\n\n - Position your cursor over the **sharedflows** folder in your local\n workspace and click\n .\n\n - Select **View \\\u003e Command Palette** to open the Command palette and select **Cloud Code: Create Apigee shared flow bundle**.\n\n The Create shared flow wizard opens.\n2. Enter a unique name for the shared flow at the prompt and press \u003ckbd\u003eEnter\u003c/kbd\u003e.\n\nAfter you complete the steps in the wizard, the new shared flow name appears\nunder **sharedflows** in the Apigee section. Each shared flow folder is structured as described in [Shared flow bundle directory structure](/apigee/docs/api-platform/reference/shared-flow-bundle-configuration-reference#sharedflowbundlestructure)\n\nUploading a shared flow bundle\n------------------------------\n\nTo upload a shared flow bundle using Apigee in Cloud Code:\n\n1. Perform one of the following actions:\n\n - In your local workspace, position your cursor over the **sharedflows** folder and click .\n\n - Select **View \\\u003e Command Palette** to open the Command palette and select **Cloud Code: Import Apigee shared flow bundle**.\n\n2. Navigate to the shared flow bundle that you want to upload and click **Import shared flow** .\n The shared flow bundle must be structured as described in [Shared flow bundle directory structure](/apigee/docs/api-platform/reference/shared-flow-bundle-configuration-reference#sharedflowbundlestructure).\n\n3. (Optional) By default, the name of the zip file minus its extension is used for the name of the shared flow. If this name is not unique, you are prompted to enter a unique name.\n\nThe uploaded shared flow folder is added under **sharedflows** in your Apigee workspace.\n\nConfiguring shared flows\n------------------------\n\nConfigure shared flows as described in the following topics:\n\n- [Creating reusable shared flows](/apigee/docs/api-platform/fundamentals/shared-flows)\n- [Adding features using policies](/apigee/docs/api-platform/local-development/vscode/manage-policies)\n- [Managing resources](/apigee/docs/api-platform/local-development/vscode/manage-resources)\n\nUsing shared flows\n------------------\n\nYou can call a shared flow using the FlowCallout policy, as described in [FlowCallout policy](/apigee/docs/api-platform/reference/policies/flow-callout-policy).\n\nIn addition, by attaching a shared flow to a flow hook you can execute the shared flow before a proxy or target request, or after a proxy or target response. For more information, see:\n\n- [Attaching a shared flow using a flow hook](/apigee/docs/api-platform/fundamentals/flow-hooks) (conceptual overview)\n- [Attaching shared flows using flow hooks (flowhooks.json)](/apigee/docs/api-platform/local-development/vscode/deploy-environment#attaching_shared_flows_using_flow_hooks_flowhooksjson) (steps using Apigee in Cloud Code)\n\n\u003cbr /\u003e\n\n| **Note:** Apigee does not validate the dependencies between shared flows and API proxies at deploy time. For example, if the FlowCallout policy in an API proxy references a shared flow that either doesn't exist or isn't deployed, API proxy deployment still succeeds. When Apigee checks the dependency at runtime and validation fails, Apigee throws an API proxy error with a `500` HTTP status code."]]
.
.