🚨Action required for GitOps users Hello! This is our follow up to the notification from last release that there are breaking changes in the software YAML for Fleet v4.74.0. Please ignore if you are not a GitOps user. It would also be helpful if you can let us know in a comment so we can update our records on GitOps vs non GitOps deployments. 🙏Instructions for migration: https://github.com/fleetdm/fleet/blob/main/cmd/gitops-migrate/README.md Notes for troubleshooting: Make sure to start with a GitOps configuration that runs successfully on your current version. It's always a good idea to make a backup of all files.You will want to do this in two stages ( first:gitops-migrate format and then:gitops-migrate migrate ).NOTE: Don't re-add comments at this point because they'll be removed in the next step again.For the migrate step we would recommend doing that migration, then creating a PR and making any subsequent modifications to that branch (like re-adding comments), and keeping the changes staged on that branch until you've upgraded to 4.74.0. Trying to run GitOps with the migrated yaml files will fail with Fleet server and fleetd versions earlier than v4.74.The binary has been tested on macOS(ARM), Windows(x64), and Ubuntu(AMD). On Windows, remember to use \ instead of / in the commands.If errors are encountered when formatting or migrating, it does give the name of the yaml file so you can take a look at the file to figure out what might be going wrong. The only package yamls that will be migrated are those referenced in team yaml files. It will pull the relevant keys out of the package yaml and put them in the team yaml for the associated package. So if there are any package yamls that are not currently referenced by a team, those will not be migrated and will need to be adjusted once they are added to a team.Please let us know if anything unexpected happens so we can address it right away.

hey folks! just a heads up and reminder again if you're upgrading to 4.74 which was released early this week, there are some yaml breaking changes on the gitops front. we made the migration to the new yaml format much much easier. if you pre-staged your changes, please see new instructions here: https://github.com/fleetdm/fleet/tree/main/tools/gitops-migrate