Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store per-tenant flags separately from other flags #1940

Open
RebeccaMahany opened this issue Nov 5, 2024 · 0 comments
Open

Store per-tenant flags separately from other flags #1940

RebeccaMahany opened this issue Nov 5, 2024 · 0 comments

Comments

@RebeccaMahany
Copy link
Contributor

RebeccaMahany commented 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.

@RebeccaMahany 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 RebeccaMahany changed the title Store per-tenant flags separately from per-device flags Store per-tenant flags separately from other flags Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant