Can end task instance from trigger

[dstandish]

With this change, if desired, we can avoid having to resume the task on a worker. We can end the task (in states success, failed, or skipped) from the trigger itself.

Closes: #31718

cc @Lee-W

[uranusjr]

Why is this needed? I imagine this should work:

Suggested change

	def __init__(self, *, xcom_return: Any | None = None, other_xcom: dict[str, Any] | None = None, **kwargs):
	if "payload" in kwargs:
	raise ValueError("Param 'payload' not supported for this class.")
	def __init__(self, *, xcom_return: Any | None = None, other_xcom: dict[str, Any] | None = None) -> None:

[dstandish]

Because the payload is determined by the state / controlled by the class. User should not submit a payload.

[dstandish]

if we do not check, user might pass payload and it would be silently ignored

[uranusjr]

I don’t think so? The suggested change removed payload altogether and should raise TypeError when it is provided. Or is the issue you want to allow **kwargs? But I don’t see any subclass using that either.

[dstandish]

Ah i see what you're saying... Well it's in the base class. Would you not say it's probably a good idea to include kwargs in the subclasses for future compat?

[dstandish]

ok made all changes except checking for user-supplied 'payload'

[dstandish]

marking this draft for now because we have to deal with callbacks and email

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.