Skip to content

CRE-6535: remove unused web-api-trigger/target gateway handler code - #23728

Open
bolekk wants to merge 2 commits into
developfrom
worktree-cre-6535-deprecate-webapi-handler
Open

CRE-6535: remove unused web-api-trigger/target gateway handler code#23728
bolekk wants to merge 2 commits into
developfrom
worktree-cre-6535-deprecate-webapi-handler

Conversation

@bolekk

@bolekk bolekk commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

Removes the legacy web_api_trigger/web_api_target methods and their supporting node- and gateway-side code, now that these capabilities have no live deployment path (superseded by http-trigger/http-action).

  • Deletes core/capabilities/webapi/trigger, .../target, and the webapicap schema/generated types that only they used
  • Deletes the standalone dev scripts for invoking the trigger
  • Strips MethodWebAPITrigger/MethodWebAPITarget/MethodComputeAction handling, the legacy callback-pruning machinery, and HandleLegacyUserMessage's trigger logic from the gateway capabilities handler (workflow_syncer, used by V2 artifact fetching, are untouched)
  • Drops the __builtin_web-api-trigger/target wiring from the standardcapabilities delegate
  • Removes the WebAPITrigger/WebAPITarget job-spec template types from deployment/cre/jobs

NOTE: This handler is still used for workflow artifact fetching. The next step is to migrate that functionality into the HTTP handler.

https://smartcontract-it.atlassian.net/browse/CRE-6535

Deployment Validation:

  1. Deploy a new workflow and confirm that it was fetched and started without issues.

@github-actions

github-actions Bot commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

CORA - Pending Reviewers

Codeowners Entry Overall Num Files Owners
* 5 @smartcontractkit/foundations, @smartcontractkit/core
/core/capabilities/ 15 @smartcontractkit/keystone, @smartcontractkit/capabilities-team
/core/services/workflows/ 1 @smartcontractkit/keystone
/core/services/standardcapabilities/ 1 @smartcontractkit/keystone
/deployment/cre/ 3 @smartcontractkit/keystone, @smartcontractkit/operations-platform
go.mod 6 @smartcontractkit/core, @smartcontractkit/foundations
go.sum 6 @smartcontractkit/core, @smartcontractkit/foundations
integration-tests/go.mod 1 @smartcontractkit/core, @smartcontractkit/devex-tooling, @smartcontractkit/foundations
integration-tests/go.sum 1 @smartcontractkit/core, @smartcontractkit/devex-tooling, @smartcontractkit/foundations

Legend: ✅ Approved | ❌ Changes Requested | 💬 Commented | 🚫 Dismissed | ⏳ Pending | ❓ Unknown

For more details, see the full review summary.

@github-actions

Copy link
Copy Markdown
Contributor

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

  • #added For any new functionality added.
  • #breaking_change For any functionality that requires manual action for the node to boot.
  • #bugfix For bug fixes.
  • #changed For any change to the existing functionality.
  • #db_update For any feature that introduces updates to database schema.
  • #deprecation_notice For any upcoming deprecation functionality.
  • #internal For changesets that need to be excluded from the final changelog.
  • #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
  • #removed For any functionality/config that is removed.
  • #updated For any functionality that is updated.
  • #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

@github-actions

Copy link
Copy Markdown
Contributor

✅ No conflicts with other open PRs targeting develop

@trunk-io

trunk-io Bot commented Sep 12, 2026

Copy link
Copy Markdown

Static BadgeStatic BadgeStatic Badge

Failed Test Failure Summary Logs
Test_CCIPTokenTransfer_Solana2Sui_BurnMintTokenPool_ZeroTokenReceiver_Revert The test failed during a Solana blockchain setup, likely due to an issue with the environment or container initialization. Logs ↗︎
Test_CCIP_TokenTransfer_Aptos2EVM The test failed because the Aptos node API could not be accessed on port 8080, which is the only port it can be exposed on. Logs ↗︎

View Full Report ↗︎Docs

Removes the legacy web_api_trigger/web_api_target methods and their
supporting node- and gateway-side code, now that these capabilities
have no live deployment path (superseded by http-trigger/http-action).

- Deletes core/capabilities/webapi/trigger, .../target, and the
  webapicap schema/generated types that only they used
- Deletes the standalone dev scripts for invoking the trigger
- Strips MethodWebAPITrigger/MethodWebAPITarget handling, the legacy
  callback-pruning machinery, and HandleLegacyUserMessage's trigger
  logic from the gateway capabilities handler (compute_action and
  workflow_syncer, used by V2 artifact fetching, are untouched)
- Drops the __builtin_web-api-trigger/target wiring from the
  standardcapabilities delegate
- Removes the WebAPITrigger/WebAPITarget job-spec template types from
  deployment/cre/jobs
- go mod tidy (both modules) to drop go-jsonschema and other deps that
  were only pulled in by the deleted webapicap generator

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@bolekk
bolekk force-pushed the worktree-cre-6535-deprecate-webapi-handler branch from 031b498 to c1458d0 Compare September 13, 2026 02:08
@cl-sonarqube-production

Copy link
Copy Markdown

@bolekk
bolekk marked this pull request as ready for review September 13, 2026 02:51
@bolekk
bolekk requested review from a team as code owners September 13, 2026 02:51
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