So a

.pkg

with a unique secret for group A, one for group B, etc.?

Sounds right.

Thanks @zwass. Just a follow up question. In the doc the first secret in the spec is labeled as

default

. Is the

default

label what the spec expects for the "main" enrollment secret value or can I set that label to whatever I want?

You can set it to whatever you want. After you run the DB migration your existing secret will become

default

, but there's no need for a

default

.

👍 . So steps are to - 1) Create the spec 2) Submit it to fleet with

fleetctl

3) run the DB migration?

No, you'll need to update Fleet and run the migrations first

Ah I just updated Fleet to

2.6.0

and ran a migration. So I can just create a spec?

Right now that commit is not yet in a release. Just

master

.

Ah now I see that that functionality was committed after the

2.6.0

release, apologies. Do you have an anticipated release date for that feature? And thank you for answering these questions now and many, many times before.

Yeah I think I can probably cut a release sometime in the next week.

Thank you Zach 🍻