|author||Nobel Barakat <email@example.com>||Fri Feb 17 21:45:41 2023 +0000|
|committer||Nobel Barakat <firstname.lastname@example.org>||Fri Feb 17 23:46:35 2023 +0000|
policymanager: stop GetDefaultInstanceConfigFromBase from overriding fluent bit value The function `GetDefaultInstanceConfigFromBase` in `manager.go` is overriding the default value for fluent bit causing tests to fail. Adding a line to support flunet-bit. BUG=b/268738844 TEST=presubmit RELEASE_NOTE=none Change-Id: I4ac95d229833404f73d9107c61c7af23b5e41c9d
Policy Manager is the client for the COS control plane. It is responsible for reporting current instance status and fetching device update config.
It is designed to be a system daemon that's started immediately after boot. It sends status update to an update manager, which will respond with the appropriate update config.
Using the update config, it will generate the appropriate update policy blobs to enforce the update strategy set by the user.
Part of Policy Manager's features is to allow users to control the OS update behavior of their COS instances.
Instances will only receive updates within their major release version. For example, if both 12.1.0 and 13.0.0 are available, an instance running 12.0.0 will only get updated to 12.1.0 if it has this strategy.
The actual enforcement of the strategies are done by the update policy, which is a Chrome OS feature. An update policy is a protobuf blob that contains the parameters that will be used to fetch updates from Omaha. Policy Manager is responsible for deciding when to enable or disable the update engine.
FEATURES=test emerge-lakitu policymanager