Hey, I am trying to migrate our Fleet config over to GitOps and noticed the

fleet-gitops

repo was archived on Jul 29. The README points to

fleetctl new

instead, which we're using, so mostly just want to check we're reading that right. Two things I'd like to confirm. Is

fleetctl new

now the only supported starting point, or is the archived repo still a valid reference for the CI setup? The archived repo had

gitops.sh

and

gitops-fleets.sh

, and I want to know whether those are still the recommended approach for a GitLab pipeline or whether they've been superseded. Also,

fleetctl generate-gitops

returns "You are not authorized to run this command" with an API-only user on the GitOps role. Looks like that's expected given GitOps is write-only, so the export needs an admin credential. Is that right, or is

generate-gitops

meant to work with a GitOps-role token?

hmmm. i wonder. I've used that repo many times in the past cause I couldn't find proper docs. Is there another reference implemenation we can use?

Hi Stefan(s)!

fleetctl new

is the currently recommended starting point for standing up an instance of Fleet using Gitops. The

fleet-gitops

repo is maintained for backwards compatibility and will still continue to function, but will not receive updates. You should use an admin account to run

fleetctl generate-gitops

(intentionally designed this way since the config created contains some sensitive info) and a GitOps role-assigned user to perform your applies. Our GitOps documentation should cover the configuration portion, and the readme for

fleetctl new

should cover setting up the workflow (github.com/fleetdm/fleet/blob/…/README.md#…).

^^ seems like another a breaking change for those of us who use mature gitops pipelines and cannot migrate without significant investment of time 😐 Are there plans to comprehensively document gitops functionality?