Skip to content

Harden Integration Data Updater and alert on failure - #2046

Closed
David Pine (IEvangelist) wants to merge 2 commits into
mainfrom
ievangelist-fix-integration-data-updater-f80
Closed

David Pine (IEvangelist) wants to merge 2 commits into
mainfrom
ievangelist-fix-integration-data-updater-f80

Conversation

@IEvangelist

Copy link
Copy Markdown
Member

Summary

Related to #1960 and #1961. The Integration Data Updater has failed daily since #1895 without anyone noticing.

  • Read optional catalog fields (apiReference, title, version) via PSObject.Properties in generate-package-json.ps1 so Set-StrictMode -Version Latest no longer throws on missing properties. Omitted apiReference is included; only explicit false is excluded.
  • Add a "Report failure" step to update-integration-data.yml: on a failed scheduled run it opens (or comments on) a single "Integration Data Updater is failing" issue. The job gets issues: write for this.

This overlaps with the predicate change in #1961, so one of the two will need a rebase.

Third-party links and affiliations

None.

Validation

  • Predicate checked under StrictMode against omitted/false/true fixtures: returned the expected entries.
  • PowerShell parser on generate-package-json.ps1: 0 errors.
  • Full updater run and the failure-alert step were not run; they need a post-merge workflow_dispatch/scheduled run (the alert step only fires on scheduled failures).

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot AI balanced review requested due to automatic review settings November 4, 2026 11:46
@IEvangelist

Copy link
Copy Markdown
Member Author

Folded into #1961.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The failure reporter shares the updater’s 45-minute job timeout, so a timed-out scheduled run can terminate before reporting and produce no alert.

1 open issue
What changed in this PR

This PR fixes optional catalog-field handling in the Integration Data Updater and adds issue-based alerts for scheduled failures, addressing the failure described in #1960.

Changes:

  • Read optional apiReference, title, and version fields safely under PowerShell StrictMode.
  • Preserve entries with omitted or true apiReference; exclude explicit false values.
  • Create or comment on a tracking issue when a scheduled update fails.
File Description
src/​tools/​PackageJsonGenerator/​generate-package-json.ps1 Safely handles optional catalog properties under StrictMode.
.github/​workflows/​update-integration-data.yml Adds failure reporting and issue-write permission.

Review effort: Balanced

Comment on lines +181 to +182
- name: Report failure
if: ${{ failure() && github.event_name == 'schedule' }}
@aspire-repo-bot

Copy link
Copy Markdown
Contributor

Frontend HTML artifact ready

The latest frontend build uploaded the frontend-dist artifact for PR #2046. Use the VS Code button below to open this PR with GitHub Artifacts Explorer and browse the built HTML locally.

VS Code: Open PR #2046 artifacts

This comment updates automatically when a new frontend build artifact is uploaded.

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.

2 participants