Anchorage API reference
    Preparing search index...

    Per-execution runtime handed to execute/dryRunExecute as the third argument. fetch is bound to the manifest's declared egress: every actual request — redirect hops included — must resolve to a declared host or it is denied (ConnectorPolicyError, policy 'egress-fetch') and audited. This is the runtime half of the egress posture (the networkEgress policy gates the declared list; this guard pins actual requests to it), so actual ⊆ declared ⊆ org-allowed. A manifest with no egress gets a fetch that denies everything. A vendor SDK carrying its own HTTP stack bypasses the guard — route its traffic through this fetch (most SDKs accept a fetch/transport option) or that connector's egress posture degrades to declaration-only.

    interface ConnectorRuntime {
        fetch: EgressGuardedFetch;
    }
    Index

    Properties

    Properties

    Fetch guarded by the connector manifest's declared egress hosts.