FAAST Output Report

Present

1-min readUpdated May 11, 2026

Copied Raw Markdown!

This note records outputs generated from samples/FAAST-ZIP2P_LIDET_BL_GET with LLM-backed planning enabled.

Output FoldersURL copied

  • Mule app: samples/FAAST-ZIP2P_LIDET_BL_GET-output
  • Mule custom policy: samples/FAAST-ZIP2P_LIDET_BL_GET-output-custom-policy
  • Flex GitOps: samples/FAAST-ZIP2P_LIDET_BL_GET-output-flex-gitops

Mule AppURL copied

The Mule app lane emits one flow or sub-flow XML per source policy plus app wiring.

Flow orchestration output:

ApiGeeToMuleSoft/samples/FAAST-ZIP2P_LIDET_BL_GET-output/src/main/mule/FC-Authentication.xml
<mule xmlns="http://www.mulesoft.org/schema/mule/core"
      xmlns:http="http://www.mulesoft.org/schema/mule/http"
      xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core" 
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <http:listener-config name="HTTP_Listener_Config"><http:listener-connection host="${http.listener.host}" port="${http.listener.port}"/></http:listener-config>
  <http:request-config name="SAP_Backend_Config" basePath="${sap.backend.basePath}"><http:request-connection protocol="HTTPS" host="${sap.backend.host}" port="${sap.backend.port}"/></http:request-config>
  <flow name="fc-authentication-flow">
    <http:listener config-ref="HTTP_Listener_Config" path="${api.listener.path}" allowedMethods="GET"/>
    <flow-ref name="ba-authentication-subflow"/>
    <flow-ref name="kvm-sapbrimcred-subflow"/>
    <flow-ref name="get-csrf-token-subflow"/>
    <flow-ref name="assign-csrf-token-subflow"/>
    <http:request config-ref="SAP_Backend_Config" method="GET" path="${sap.backend.targetPath}">
      <http:headers><![CDATA[#[{'X-CSRF-Token': vars.csrfToken default 'fetch','Authorization': 'Basic ' ++ (((vars.sapUsername default '') ++ ':' ++ (vars.sapPassword default '')) as Binary toBase64)}]]]></http:headers>
      <http:query-params><![CDATA[#[attributes.queryParams]]]></http:query-params>
    </http:request>
    <ee:transform><ee:message><ee:set-payload><![CDATA[%dw 2.0
output application/json
---
payload]]></ee:set-payload></ee:message></ee:transform>
    <error-handler ref="auth-error-handler"/>
  </flow>

Mule Custom PolicyURL copied

The custom-policy lane generated a strong header-injection policy for the AssignMessage case, and the warning text is now planner-aware instead of generic.

Generated policy descriptor:

ApiGeeToMuleSoft/samples/FAAST-ZIP2P_LIDET_BL_GET-output-custom-policy/policies/am-assigncsrftoken/policy.yaml
id: am-assigncsrftoken
name: am-assigncsrftoken
description: Generated header injection custom policy from AssignMessage source.
category: Governance

resourceLevelSupported: true
standalone: true
type: custom

configuration:
  - propertyName: enabled
    name: Enable Policy
    description: Toggle header injection.
    type: boolean
    defaultValue: true
    optional: false

pointcut:
  methodRegex: ".*"
  uriTemplateRegex: "/*"

Flex GitOpsURL copied

The Flex lane generated one direct policy and left the rest as manual-review notes, which is the right behavior for this sample.

Generated Flex summary:

ApiGeeToMuleSoft/samples/FAAST-ZIP2P_LIDET_BL_GET-output-flex-gitops/README.md
# Flex GitOps Assets for FAAST-ZIP2P_LIDET_BL_GET

Generated structure:
- `api/api-instance.yaml`
- `api/api-definition.yaml`
- `policies/*.yaml`
- `gateway/flex-gateway-config.yaml`
- `cicd/pipeline.yaml`

Base path: `/faast/v1/zip2p_lidet_bl_get`
Upstream URL: `http://abc.com`

Generated policies:
- `am-assigncsrftoken` -> `header-injection`

Manual review:
- BA-Authentication: BasicAuthentication needs Mule app or custom policy handling, not direct Flex GitOps policy generation.
- FC-Authentication: FlowCallout needs Mule app or custom policy handling, not direct Flex GitOps policy generation.

ReadURL copied

  • AM-ASSIGNCSRFTOKEN maps cleanly into policy-style output.
  • BA-Authentication, FC-Authentication, KVM-SAPBRIMCRED, and SC-GetCSRFToken are still app logic, not clean gateway policy conversions, and the planner now says why.