Skip to content

Remove the workflows component abstraction - #4478

Open
JoshVanL wants to merge 6 commits into
dapr:mainfrom
JoshVanL:remove-workflows-abstraction
Open

Remove the workflows component abstraction#4478
JoshVanL wants to merge 6 commits into
dapr:mainfrom
JoshVanL:remove-workflows-abstraction

Conversation

@JoshVanL

Copy link
Copy Markdown
Contributor

The workflows package only ever defined an interface and its request/response types: no concrete component implementation ever existed in this repository. The single implementation lives inside dapr/dapr, which now uses the durabletask-go client directly, so the abstraction serves no purpose and makes client changes require updates to two repositories.

Deletes the workflows package, its conformance test harness and config, and the workflows entries in the metadata utils, the metadata analyzer, the component metadata schema (regenerated), and the component folders list.

The workflows package only ever defined an interface and its
request/response types: no concrete component implementation ever
existed in this repository. The single implementation lives inside
dapr/dapr, which now uses the durabletask-go client directly, so the
abstraction serves no purpose and makes client changes require updates
to two repositories.

Deletes the workflows package, its conformance test harness and config,
and the workflows entries in the metadata utils, the metadata analyzer,
the component metadata schema (regenerated), and the component folders
list.

Signed-off-by: joshvanl <me@joshvanl.dev>
@JoshVanL
JoshVanL requested a review from Copilot July 28, 2026 17:27
@JoshVanL
JoshVanL requested review from a team as code owners July 28, 2026 17:27
@JoshVanL JoshVanL added the autoupdate automatically keeps PR up to date against master label Jul 28, 2026

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.

Pull request overview

Removes the unused workflows component abstraction from components-contrib (interface + request/response/metadata types) along with its conformance test scaffolding and associated metadata/schema tooling entries, since there is no concrete workflows component implementation in this repo and the dapr runtime no longer needs this abstraction.

Changes:

  • Deleted the workflows package (interface/types/docs) and workflows conformance tests/config.
  • Removed workflows from component-type metadata utilities, metadata analyzer generation, component folder list, and the component metadata JSON schema.
  • Regenerated schema-related artifacts to reflect the removed component type.

Reviewed changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
workflows/workflow.go Deletes the workflows component interface definition.
workflows/requests.go Deletes workflows request type definitions.
workflows/responses.go Deletes workflows response type definitions.
workflows/metadata.go Deletes workflows metadata struct wrapper.
workflows/README.md Removes workflows package documentation.
tests/conformance/workflows/workflows.go Removes workflows conformance test harness.
tests/conformance/workflow_test.go Removes workflows conformance test entrypoint.
tests/config/workflows/tests.yml Removes workflows conformance test configuration.
metadata/utils.go Removes workflows from the valid component types list.
component-metadata-schema.json Removes workflows from the schema’s allowed type enum.
.build-tools/pkg/metadataschema/schema.go Removes workflows from the schema generator’s type enum.
.build-tools/pkg/metadataanalyzer/utils.go Removes workflows handling from metadata analyzer generator logic.
.build-tools/component-folders.yaml Removes workflows from the component folders list.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 113 to 115
case "configuration":
method, methodFinderErr = getConstructorMethod("configuration.Store", parsedFile)
if methodFinderErr == nil {
// Component type, of one of the allowed values.
Type string `json:"type" yaml:"type" jsonschema:"enum=bindings,enum=state,enum=secretstores,enum=pubsub,enum=workflows,enum=configuration,enum=lock,enum=middleware,enum=crypto,enum=nameresolution,enum=conversation"`
Type string `json:"type" yaml:"type" jsonschema:"enum=bindings,enum=state,enum=secretstores,enum=pubsub,enum=configuration,enum=lock,enum=middleware,enum=crypto,enum=nameresolution,enum=conversation"`
// Name of the component (without the inital type, e.g. "http" instead of "bindings.http").
Comment on lines 208 to 212
"bindings",
"state",
"secretstores",
"pubsub",
"workflows",
"configuration",
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autoupdate automatically keeps PR up to date against master

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants