Hi Anurag, Thanks for that clarification...
Darren. Anurag S. Maskey wrote: > > Darren Kenny wrote: >> hi Renee, >> >> Renee Danson wrote: >> >>> Hi Darren, >>> >>> This is the conflict I ran across a few days back. The push I just did >>> included part of the fix (there are now nwam_ncu_enable/disable functions), >>> but the under-the-hood bits in nwamd still need to get plugged in once >>> Michael's push goes in; that should be a very minor update. >>> >>> We'll also need to update nwamadm to allow this to happen from the command- >>> line. >>> >>> The property will remain read-only; you shouldn't toggle it via the property >>> settings. You should instead use the enable/disable functions. This seemed >>> more consistent with the distinction between configuration and >>> administration >>> that we already have in the CLI, and also makes more sense in the event >>> flow, >>> I think. >>> >> I'm still a little confused though, does calling ncu_enable set the default >> mode >> (for on-boot behaviour) and activate it immediately, or just one of those. >> > should do both. When any object with manual activation-mode is enabled, > it is immediately enabled and the the "enabled" property is set to > "true". So, in the next reboot (or restart of nwam), the "enabled" > property is checked and if true, is enabled. (You can try with location > and enms with manual activation-mode). > > Anurag >
