Skip to content

fix: coerce list-of-custom-type effector inputs supplied as YAML#1433

Open
zan-mateusz wants to merge 1 commit into
apache:masterfrom
zan-mateusz:fix/coerce-list-custom-type-effector-yaml
Open

fix: coerce list-of-custom-type effector inputs supplied as YAML#1433
zan-mateusz wants to merge 1 commit into
apache:masterfrom
zan-mateusz:fix/coerce-list-custom-type-effector-yaml

Conversation

@zan-mateusz

Copy link
Copy Markdown
Contributor

Invoking an effector whose parameter is a list of a registered (TOSCA) data type failed to coerce the supplied value. Two fixes:

  • Parse YAML block-list strings ("- item" lines) into a list of elements for non-string element types, instead of collapsing the whole block into a single string (CommonAdaptorTypeCoercions).
  • Run effector parameter coercion in the entity's execution context so registered bean types can resolve their management context, instead of failing with "... without a management context" (Effectors).

Invoking an effector whose parameter is a list of a registered (TOSCA) data
type failed to coerce the supplied value. Two fixes:

- Parse YAML block-list strings ("- item" lines) into a list of elements for
  non-string element types, instead of collapsing the whole block into a
  single string (CommonAdaptorTypeCoercions).
- Run effector parameter coercion in the entity's execution context so
  registered bean types can resolve their management context, instead of
  failing with "... without a management context" (Effectors).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.

1 participant