Skip to content

Use explicit Azure trigger sync for partial inventories - #28

Merged
jeremydixon22 merged 1 commit into
mainfrom
fix/azure-explicit-trigger-sync
Aug 11, 2026
Merged

Use explicit Azure trigger sync for partial inventories#28
jeremydixon22 merged 1 commit into
mainfrom
fix/azure-explicit-trigger-sync

Conversation

@jeremydixon22

Copy link
Copy Markdown
Member

Summary

  • replace the ineffective restart-only recovery for a persistent partial Flex inventory with Azure's explicit syncfunctiontriggers action
  • keep the recovery bounded to one attempt and still require the exact packaged runtime inventory and end-to-end behaviors
  • add redacted diagnostic evidence containing only public function identifiers and the deployment-attempt count
  • cover immediate success, empty inventory, persistent partial inventory, successful trigger-sync recovery, and trigger-sync failure with full cleanup assertions

Evidence

  • scripts/test-validate-azure-durable-functions-live.sh
  • shell syntax and ShellCheck
  • CI classifier/export/wrapper regression tests
  • deterministic public-export rehearsal: 854 files, matching tree hashes, secret/ownership/history scans passed

The preceding hosted run deployed successfully and issued a restart, but the authenticated runtime stayed at 1 of 7 functions for more than four additional minutes. This PR uses the direct trigger-registration operation documented for that failure boundary rather than adding unbounded polling or generic retries.

@jeremydixon22
jeremydixon22 merged commit 8825efd into main Aug 11, 2026
13 checks passed
@jeremydixon22
jeremydixon22 deleted the fix/azure-explicit-trigger-sync branch August 11, 2026 15:25
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