You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some agent flags are applicable to a device regardless of which tenant it's under -- for example, a device can only ever have one pinned launcher version, not multiple.
Other flags, however, can have multiple valid values for a multitenant launcher installation. For example, the osquery and osquery watchdog flags can differ per-tenant since we will run a different osquery instance per tenant.
Flags that are per-tenant rather than global should be stored as such.
This change must be backwards compatible.
The text was updated successfully, but these errors were encountered:
RebeccaMahany
changed the title
Split up how we store and set flags that are per-tenant instead of per-device. These are potentially limited just to osquery flags and osquery watchdog flags (enabled, memory limit, utilization limit, delay). This change must be backwards compatible.
Store per-tenant flags separately from per-device flags
Nov 5, 2024
RebeccaMahany
changed the title
Store per-tenant flags separately from per-device flags
Store per-tenant flags separately from other flags
Nov 5, 2024
Some agent flags are applicable to a device regardless of which tenant it's under -- for example, a device can only ever have one pinned launcher version, not multiple.
Other flags, however, can have multiple valid values for a multitenant launcher installation. For example, the osquery and osquery watchdog flags can differ per-tenant since we will run a different osquery instance per tenant.
Flags that are per-tenant rather than global should be stored as such.
This change must be backwards compatible.
The text was updated successfully, but these errors were encountered: