qq - I saw the 'global queries' and merge queries change announcement https://osquery.slack.com/archives/C01DXJL16D8/p1690301752005349 I've tried making sense of this via github but wasn't really sucessful e.g this https://github.com/fleetdm/fleet/pull/13078 Can someone explain the impact for this Our scenario is we manage packs and queries via packs via api pipeline. [Fleet 4.30.1 in kube gcp. No premium license] More specifically we have a prod label set and uat label set and uat/prod pack targeted to those labels to be able to test new content we declare the labels, and packs + queries as yaml and then push them via/check current state vs git

/api/latest/fleet/packs
/api/latest/fleet/packs/schedule
/api/latest/fleet/labels
/api/latest/fleet/queries
/api/latest/fleet/queries/{query['id']}
/api/latest/fleet/packs/{pack['id']}
/api/latest/fleet/labels/{label_id}

with global scheduled queries disabled We also occasionally use the https://meow.meow/packs/manage ui to spot check (yes i understand this is errr deprecated]

Hi @Vlad Previn! The packs functionality is still there for backwards compatibility! We just changed things about to make managing queries and schedule more streamlined and get back to using Packs as they were originally intended (a fast way to import groups of queries). There are some changes to the Queries Api.

upgrade-packs

is a tool to help with the transition from Packs to Schedule, but isn't something you're required to do.

i see thanks Kathy. Hmm so we're not required to re-enable global queries ?