Skip to content

Distinguish invalid Dag access control from FAB backend failures - #74788

Open
ephraimbuddy wants to merge 1 commit into
mainfrom
dag-processor-fab-validation
Open

ephraimbuddy wants to merge 1 commit into
mainfrom
dag-processor-fab-validation

Conversation

@ephraimbuddy

@ephraimbuddy ephraimbuddy commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Report malformed Dag access-control definitions as validation errors. Backend failures keep their original exception type, allowing atomic parse publication to reject invalid metadata while retrying infrastructure failures.

Layer 1 of the seven-part replacement for #74233, in GitHub native stack #74792. Base: main. This prerequisite can be merged independently.

GitHub's Files changed tab shows this layer. Compare this layer.

Merge order:

  1. FAB validation
  2. Source consistency
  3. Publication API
  4. Durable work delivery
  5. HTTP manager
  6. Complete processor API mode
  7. Helm and Compose deployment

Was generative AI tooling used to co-author this PR?
  • Yes — Codex (GPT-6)

Generated-by: Codex (GPT-6) following the guidelines

Callers need to distinguish malformed Dag access control from permission
backend failures so they can report invalid input without suppressing
transient infrastructure errors. Existing FabException handlers remain
compatible.
@ephraimbuddy
ephraimbuddy force-pushed the dag-processor-fab-validation branch from 6bb9d0c to d11b39e Compare October 16, 2026 15:35

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant