As of now we are not populating the sync state during the registration process.

(Hidden) GLobal Flag  : Determines initial state of sync TO UNSYNCRONIZED / NON-REQUESTED

Onap default global flag 'cache enabled' true -> all cmhandles initial state will be UNSYNCHRONIZED
Ericsson default global flag 'cache enabled' false -> all cmhandles initial state will be NONE_REQUESTED

Set both the flag and enum after module sync

The requirement is to have a value (NONE_REQUESTED or UNSYNCHRONIZED) i.e a valid value from SyncStateEnum during the cmHandle registration process.

Open questions : 

1. if the datasync state is a mandatory parameter. 
   if yes then do we need to restrict the value.
   if no , then what would be the default state (NONE_REQUESTED or UNSYNCHRONIZED) ??
2. Is data sync enabled also set as part of registration of cm handle.
3. Even if dataSyncEnabled is false and we pass in the state enum value then whether it should ignore/ go with default value (depends on #1)
4. During the cmHandleRegistration update request(updating dmi/public properties) , can it have any effect on the data sync state?

A/C:

1. The provided dataSyncState should be persisted.
2. Check the compositeState API if it returns the dataSyncState as well.
3. Add necessary values to OOM Helm chart
4. Demo to the team.
5. Update documentation

Out of Scope: 

1. Don't work on the data sync state transitions ( eg : NONE_REQUESTED to UNSYNCHRONIZED)
2. Validation is not required ( pre-assuming the input is valid as it is present in the docs as well)