When the deployments service detects that device asking for an update has same artifact (with same artifact_name) as the one in the new deployment targeting the device, deployments service:

• returns No Content to the device;

• marks device deployment for a given device as already installed (special status);

• do not assign artifact to the devices deployment;

This task is about changing the last item from the list and start assigning artifact to device deployment, even if the service detected the artifact has already been installed.

Why:

• it’s possible to check which artifact has been selected for the device in the backend;

• it’s possible to detect that there is no artifact for the device;

• behavior is the same in OS and enterprise (currently, deployments-enterprise is assigning artifact to device deployment in this situation);
  
  

Acceptance criteria:

• assign artifact to device deployment object even if given artifact has already been installed;