Sirius interpreter vs M2Doc Interpreter behaviour

Document Generation
1

Hi all,
I am trying to use Capella and PVMT to manage the physical architecture of a system deployed to a Kubernetes cluster and I defined some extensions to handle host types, such as VM, Container, Pod, …

For the Pod I defined a specific extension which records the resources requested by the pod itself

image
image368×290 3.94 KB

aql:self.eContents(pa::PhysicalComponent)->select(pc | pc.appliedPropertyValueGroups.ownedPropertyValues->any(pv | pv.name = 'HostType').value.name.equals('Pod'))

The idea is to collect such information in tables of the M2Doc generated document.

As a first step I am trying to implement a query able to collect all pods within a cluster

aql:self.eContents(pa::PhysicalComponent)->select(pc | pc.appliedPropertyValueGroups.ownedPropertyValues->any(pv | pv.name = 'HostType').value.name.equals('Pod'))

The query in the Sirius interpreter returns the expected result

image
image981×496 11.4 KB

but its M2Doc counterpart is not working

selection.eContents(pa::PhysicalComponent)->select(pc | pc.appliedPropertyValueGroups.ownedPropertyValues->any(pv | pv.name = 'HostType').value.name.equals('Pod'))

image
image978×153 4.68 KB

The error reported is

ERROR: expression in an any must return a boolean (105, 137)

which refers to the following query fragment

->any(pv | pv.name = 'HostType')

I still have difficulties in understanding some subtle differences in the syntax of AQL queries supported by M2Doc through the M2Doc services used in this addon.

2

Just an update to share that I managed to get a working query

selection.eContents(pa::PhysicalComponent)->select(pc | pc.appliedPropertyValueGroups.ownedPropertyValues->any(pv | pv.name.equals('HostType')->first()).oclAsType(capellacore::EnumerationPropertyValue).value.name.equals('Pod')->first()).name

image
image1396×487 9.05 KB

It seems that for some reason the equals within the select and the any returns a collection.
Moverover, after the any I needed to cast the type, because it returns an AbstractPropertyValue EClass.

3

I think the main difference is the validation. M2Doc validate AQL expressions and the all template before generation where the Sirius interpreter only execute the query. The Sirius interpreter only detect runtime errors.