This repository is exploring how Apigee policy bundles can be moved into MuleSoft Flex Gateway. Apigee is the source system: it stores gateway behavior as XML policies and, for some behaviors, JavaScript files. Flex Gateway is the target system: the current target artifacts are YAML policy definitions under Adhoc/flex-gateway-policies. This page explains how the Adhoc reference material lines up so a reader can see both the product-level policy mapping and the lower-level source files that feed each target policy.
The important shape is not one file to one file. In Apigee, one business policy can be split across several files: one file may run JavaScript, another may define the failure response, and another may read configuration. In Flex Gateway, the same business policy is represented as one YAML policy definition. That is why this page has two graphs: first the policy-to-policy story, then the detailed source-file-to-policy trace.
- Source to target: many Apigee files feed one Flex Gateway YAML.
- Target to source: one Flex Gateway YAML can be traced back to all Apigee files in that policy group.