Skip to content

fix(compute-providers): add provider diagnostics - #5384

Draft
edersonbrilhante wants to merge 2 commits into
mainfrom
compute-provider-diagnostics
Draft

fix(compute-providers): add provider diagnostics#5384
edersonbrilhante wants to merge 2 commits into
mainfrom
compute-provider-diagnostics

Conversation

@edersonbrilhante

Copy link
Copy Markdown
Contributor

Description

Centralize compute-provider names and defaults, replace EC2 plugin literals with the canonical provider value, and add structured provider/capability diagnostics at pool, scale-up, scale-down, webhook, and registry boundaries.

Diagnostics avoid secrets, JIT configuration, signed webhook data, and full EC2 request payloads. Focused tests also cover provider resolution, registry consistency, capability selection, and sensitive logging behavior.

Test Plan

  • Passed focused compute-provider tests: 298/298
  • Passed control-plane tests: 345/345
  • Passed webhook tests: 83/83
  • Passed lint for compute-providers, control-plane, and webhook
  • Passed formatting validation for all changed TypeScript files
  • Passed control-plane and webhook typechecks
  • Compute-provider typecheck still reports pre-existing errors in vitest.config.ts and vitest.base.config.ts

Related Issues

N/A

@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@edersonbrilhante
edersonbrilhante force-pushed the compute-provider-diagnostics branch 7 times, most recently from 1e2df15 to 6a98b96 Compare September 7, 2026 13:18
@edersonbrilhante
edersonbrilhante force-pushed the compute-provider-diagnostics branch from 6a98b96 to c2717c0 Compare September 7, 2026 13:19
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