Use Chrome to provide remote logging permission
The Google-branded updater should use stable Chrome to infer remote
logging opt-in. Inject the permission provides as an external constant
so that it may be overridden in integration tests.
Bug: 371595849
Change-Id: Icc2c4f68d06d2bffa8543fab8292146382ea421e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6612962
Commit-Queue: Noah Rose Ledesma <[email protected]>
Reviewed-by: Joshua Pawlicki <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1468771}
diff --git a/chrome/updater/constants.h b/chrome/updater/constants.h
index 150a6c4..a84b5a6 100644
--- a/chrome/updater/constants.h
+++ b/chrome/updater/constants.h
@@ -5,6 +5,8 @@
#ifndef CHROME_UPDATER_CONSTANTS_H_
#define CHROME_UPDATER_CONSTANTS_H_
+#include <optional>
+
#include "base/time/time.h"
#include "build/build_config.h"
#include "components/update_client/update_client_errors.h"
@@ -261,6 +263,8 @@
"crx_verifier_format";
inline constexpr char kDevOverrideKeyMinumumEventLoggingCooldownSeconds[] =
"minimum_event_logging_cooldown_seconds";
+inline constexpr char kDevOverrideKeyEventLoggingPermissionProvider[] =
+ "event_logging_permission_provider";
inline constexpr char kDevOverrideKeyDictPolicies[] = "dict_policies";
// TODO(crbug.com/389965546): remove this once the checked-in old updater builds
