Skip to content

feat(controlplane): apply synced transforms in managed pipeline#172

Merged
mslipper merged 1 commit into
mainfrom
feat/managed-pipeline-transforms-sync
Jun 3, 2026
Merged

feat(controlplane): apply synced transforms in managed pipeline#172
mslipper merged 1 commit into
mainfrom
feat/managed-pipeline-transforms-sync

Conversation

@mslipper

@mslipper mslipper commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

The control plane delivers gcp_auth, hmac_sign, and oauth_token transforms bundled in a top-level transforms array on /proxy/sync, but the proxy's SyncResponse had no such field, so TransformsFromSync only ever emitted allowlist and secrets. All three transform types — oauth_token included — were silently dropped in managed mode at both startup and every reload.

This plumbs the transforms array through SyncResponse, SyncUpdate, and TransformsFromSync, appending it after allowlist+secrets so a body-mutating secret swap lands before hmac_sign signs the body (matching the canonical ordering in iron-proxy.example.yaml). The transform types are already blank-imported, so buildPipeline constructs them by name with no further changes.

The control plane delivers gcp_auth, hmac_sign, and oauth_token transforms
bundled in a top-level `transforms` array on /proxy/sync, but the proxy's
SyncResponse had no such field, so TransformsFromSync only emitted allowlist
and secrets. All three transform types — oauth_token included — were dropped
in managed mode at both startup and every reload.

Plumb the `transforms` array through SyncResponse, SyncUpdate, and
TransformsFromSync, appending it after allowlist+secrets so body-mutating
secret swaps land before hmac_sign signs the body.
@mslipper mslipper merged commit 81a3976 into main Jun 3, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant