Roll Out a Policy Change and Verify It Applied

Roll Out a Policy Change and Verify It Applied

Patch a policy with an updateMask and verify a canary device applied it.

1. Read the policy before changing it so the current version is captured and the change can be reviewed or rolled back against a known baseline.
2. Patch only the fields named in the updateMask. Without a mask the request body replaces the whole policy, silently dropping settings that were not sent, so the mask is always supplied here.
3. List the fleet to pick a canary device to watch. Every device on this policy will receive the change on its next check-in.
4. Poll the canary device until it reports the policy as applied. Devices apply policy on check-in, so a freshly patched policy is not live on the fleet until this reports back.

What you'll need to have ready

• enterpriseName: The enterprise resource name (e.g. enterprises/LC0123abcd).
• policyName: The full policy resource name to change.
• updateMask: Comma-separated field mask limiting the patch (e.g. "cameraDisabled,screenCaptureDisabled").
• cameraDisabled: Whether the device camera is disabled under the new policy.
• screenCaptureDisabled: Whether screen capture is disabled under the new policy.

For your developer

Arazzo workflow google-android:roll-out-policy-change, 4 operations: getPolicy → patchPolicy → listDevices → getDevice. Specs on APIs.io.