DaprContainer withComponent(path) incorrectly parses the type field

[joebowbeer]

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:

java-sdk/testcontainers-dapr/src/main/java/io/dapr/testcontainers/DaprContainer.java

Line 213 in daf4c8b

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

But the type is actually stored in the spec:

java-sdk/testcontainers-dapr/src/test/resources/dapr-resources/statestore.yaml

Line 6 in daf4c8b

type: state.redis

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

java-sdk/testcontainers-dapr/src/test/java/io/dapr/testcontainers/DaprComponentTest.java

Line 72 in daf4c8b

+ " type: null\n"

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: