Open pintify opened 2 years ago
I think I've found something that could point to the bug.
When you save/configure the step, it seems to check the config with DeviceConfiguration class. Whose child (DeviceConfigurationComponent requires a field id
:
However, when the job is launched, the same configuration is marshalled through KuraDeviceConfiguration class. Whose child KuraDeviceComponentConfiguration uses pid
field instead:
I don't know if there is some conversion in between.. However, is it possible this discrepancy between both formats may be behind this mashalling issue?
This issue remains on Kapua 1.6.2
The issue persists on Kapua 1.6.4
Hi, Right now on the develop branch the issue should be solved. I'll check soon if it's the case also for the last 1.6.x build
The issue seems to persist in 1.6.10
Just to verify, version 1.6.12 still has this bug
Describe the bug In version 1.5.2, the steps of type Configuration Put are unable to parse the example configuration neither other configurations based on it that were working on version 1.4.x.
To Reproduce Steps to reproduce the behavior:
See the error:
Version of Kapua 1.5.2
Type of deployment
Main component affected
Additional context Add any other context about the problem here.