Closed Mark90 closed 2 months ago
its somehow not using the domain_model_attr
to correctly connect the block relations, in the test test_migrate_domain_models_new_product_block_on_product_block
it does show it correctly in the DB, here a print of the relation table inside that test:
[
SubscriptionInstanceRelationTable(
in_use_by_id=be45114a-befc-4874-a883-cc4e5012ff82,
depends_on_id=4200db96-9fd0-4911-a040-0bd82dae5c5a,
order_id=0,
domain_model_attr=sub_block
),
SubscriptionInstanceRelationTable(
in_use_by_id=be45114a-befc-4874-a883-cc4e5012ff82,
depends_on_id=fd98ba9c-1343-489a-8811-63e478275453,
order_id=0,
domain_model_attr=sub_block_2
),
SubscriptionInstanceRelationTable(
in_use_by_id=be45114a-befc-4874-a883-cc4e5012ff82,
depends_on_id=a91ba570-ef61-4644-9971-5c1baaece405,
order_id=0,
domain_model_attr=None
)
]
Problem
Nesting product blocks is the recommended way to separate configuration into reusable blocks.
Pseudo code example:
However, referring to the same product block type more than once raises a ValueError (see below). For example:
A workaround is to change the field to a
node: list[NodeBlock]
.Reproduce
When using this example-orchestrator branch https://github.com/workfloworchestrator/example-orchestrator/pull/19/files
With the following patch
Try to create a port with 2 nodes attached. This results in:
Trying to access the subscription in the faulty state shows the following traceback:
Affected versions
2.1.2 - 2.3.0rc5