Including Lazy, Commands, Internal and Static Attributes in payload to IoT Agent Manager#793
Conversation
60f8412 to
be710a1
Compare
|
@Cerfoglg till test are not fixed, please rename to WIP: ... |
45a686e to
3ec712f
Compare
|
We are considering merging PR #831 and this PR may be impacted (see more details here). However, any potential conflict is very easy to solve (I understand @jason-fox may provide details, if needed). Is this PR still active? @Cerfoglg @chicco785 do you agree in merging PR #831 before your PR? |
|
sure, let us now when when ready |
PR #831 has been merged, so now it's ready :) The PR would need some adaptation to solve the conflicts. Basically:
(Please @jason-fox amend mi if I'm wrong) |
3ec712f to
e4dec2a
Compare
…ent to the IoT Agent Manager * Added lazy, commands, static and internal attributes to the payload sent to the IoT Agent Manager * updated tests
e4dec2a to
221b6f6
Compare
|
it looks like some already introduced support for commands and static attributes, thus this pr actually adds only lazy and internal_attributes. |
|
@fgalan this should ready for landing now |
|
any chance to merge this PR? |
A small conflict on CNR files has arisen after merging your other PR ;) We have some "sensitive" PRs queued (in the sense they could have impact in e2e behaviors). We are trying to have a full CI e2e pass after merging one PR and before merging the next PR. The CI e2e takes a long time and is executed typically by night, so we are progressing slowly. Be patient, pls... I think that sooner than later this PR will be the next one in queue :) |
fixed by 64563fb
sure! |
Fix for Issue #768