Closed noahtalerman closed 4 hours ago
@noahtalerman Do you want me to update/refactor the configuration page, or will the product team do it?
@getvictor the product team can take the documentation.
Please feel free to mark this as ready for release w/o the docs.
We'll catch this TODO as part of the "confirm and celebrate ritual."
Open docs PR is here: https://github.com/fleetdm/fleet/pull/17890
C&C: Docs are still TODO
Hey @marko-lisica just a reminder that docs are still TODO. Rachael and I are going over open stories during confirm and celebrate ritual.
@noahtalerman @marko-lisica It's crucial to merge feature documentation promptly when the feature is released. This story was completed two months ago, and until now, there have been no docs online describing best practices. Was there anything blocking this that we can avoid in the future? Maybe a new weekly ritual to review all outstanding documentation PRs would help?
Decided that @spokanemac will take on docs: https://fleetdm.slack.com/archives/C071NNMSP2R/p1715890274157719
cc @marko-lisica @lukeheath
Decided that @spokanemac will take on docs: https://fleetdm.slack.com/archives/C071NNMSP2R/p1715890274157719
For this particular case, and not all docs.
For this particular case, and not all docs.
@spokanemac Yes! This is a one-off because you've familiarized yourself with it, albeit painfully.
@noahtalerman, Heads up that JD is at capacity right now, so we won't be able to take further doc updates. The best place to offload docs is to Engineers during the planning process, although I recognize this situation is unique.
@noahtalerman I corrected some grammar and added a section to reference Organization settings. This is ready to pull out of draft and publish.
I will note that this is not what I would want for documentation of this feature if I'm a MacAdmin unfamiliar with Fleet and/or GitOps. I will do my best to bridge the gap in my dogfooding gitops article.
Thanks @spokanemac! I'm going to pick up this documentation task (assigned) to get it unstuck and merged.
Docs are merged!
Here's the new GitOps reference page: https://fleetdm.com/docs/using-fleet/gitops
cc @spokanemac @lukeheath @zayhanlon @dherder
GitOps best practice, In Fleet's cloud city it blooms, Guide for your journey.
Goal
Context
Fleet's best practice GitOps was released as beta in Fleet 4.45.
After completing this dogfooding and documenting story, the plan is to bring the feature out of beta and announce it publically.
Changes
Product
it-and-security/
top level folder.mdm_profiles/
. All these go to workstations and workstations (canary)lib/
fleetctl apply
. Clarify thatfleetctl apply
is used for imports and supported for backwards compatibility GitOps.Engineering
QA
Risk assessment
Manual testing steps
Testing notes
Confirmation