Skip to content

[CRE-6174] Engine Execution Endpoint API - #23456

Draft
agparadiso wants to merge 7 commits into
developfrom
CRE-6174_engine_execution_endpoint_api
Draft

[CRE-6174] Engine Execution Endpoint API#23456
agparadiso wants to merge 7 commits into
developfrom
CRE-6174_engine_execution_endpoint_api

Conversation

@agparadiso

@agparadiso agparadiso commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Requires

Supports

@agparadiso agparadiso changed the title chore: Engine exposes a single execution entry point that performs no… [CRE-6174] Engine Execution Endpoint API Aug 19, 2026
@github-actions

Copy link
Copy Markdown
Contributor

✅ No conflicts with other open PRs targeting develop

@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.

@agparadiso
agparadiso force-pushed the CRE-6174_engine_execution_endpoint_api branch from a515440 to dd45db2 Compare August 19, 2026 14:18
@trunk-io

trunk-io Bot commented Aug 19, 2026

Copy link
Copy Markdown

Static BadgeStatic BadgeStatic Badge

View Full Report ↗︎Docs

Comment on lines +747 to +748
// Legacy path ignores the error on purpose. startExecution already handles all errors internally. not handling here to avoid duplication.
// future dispatcher admitter (CRE-6176) will use this error.

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.

add a LifecycleHook that can be implemented to handle the error

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

addressed here

Comment thread core/services/workflows/v2/engine.go Outdated
}
}

func (e *Engine) HandleTriggerEvent(ctx context.Context, event routedTriggerEvent) error {

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.

define interface for TriggerExecutor, I think maybe Execute or ExecuteTrigger is better for the method name, thoughts?

Comment thread core/services/workflows/v2/engine.go Outdated
event capabilities.TriggerResponse
}

type routedTriggerEvent struct {

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.

remove the enqueuedTriggerEvent type as well

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

this is still used by allTriggerEventsQueueCh I'll remove it on CRE-6175

@agparadiso
agparadiso force-pushed the CRE-6174_engine_execution_endpoint_api branch from d4c68e9 to 690bf1e Compare August 20, 2026 13:12
@cl-sonarqube-production

Copy link
Copy Markdown

Quality Gate failed Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE SonarQube for IDE

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