Skip to content

DaprContainer withComponent(path) incorrectly parses the type field #1368

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
joebowbeer opened this issue May 15, 2025 · 0 comments · May be fixed by #1370
Open

DaprContainer withComponent(path) incorrectly parses the type field #1368

joebowbeer opened this issue May 15, 2025 · 0 comments · May be fixed by #1370
Labels
kind/bug Something isn't working

Comments

@joebowbeer
Copy link
Contributor

joebowbeer commented May 15, 2025

Expected Behavior

DaprContainer withComponent(path) correctly parses the type field.

Actual Behavior

DaprContainer withComponent(path) incorrectly parses the type field.

The type is read from the root level:

String type = (String) component.get("type");

But the type is actually stored in the spec:

The test currently passes because it replaces the actual type with null, but should be state.redis:

Steps to Reproduce the Problem

Change the expected type to state.redis in the DaprComponentTest and observe the failure.

NOTE: withComponent(path) is also parsing the spec.metadata incorrectly.

The expected metadata should match that in the statestore.yaml file:

    const expectedComponentYaml =
        "apiVersion: dapr.io/v1alpha1\n"
      + "kind: Component\n"
      + "metadata:\n"
      + "  name: statestore\n"
      + "spec:\n"
      + "  type: state.redis\n"
      + "  version: v1\n"
      + "  metadata:\n"
      + "  - name: keyPrefix\n"
      + "    value: name\n"
      + "  - name: redisHost\n"
      + "    value: redis:6379\n"
      + "  - name: redisPassword\n"
      + "    value: \"\"\n"

Release Note

RELEASE NOTE:

@joebowbeer joebowbeer added the kind/bug Something isn't working label May 15, 2025
@iddeepak iddeepak linked a pull request May 15, 2025 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant