Harness's gitsync offering is too basic. It had everything for the payload in a single file. It introduced challenges for us for how to separate by environment because all the environment info was in the same file as well (so we could commit changes to CI without it impacting QA or prod yet). We also couldn’t see an easy way to separate workspace setup from individual flag management. So thinking more that, some hierarchical file approach would make more sense so it isn’t a giant blob.

We would want those separated so devs aren’t accidentally impacting something they shouldn’t because they were confused what an element was in the file.

We do fully understand that approach would overwrite things done in the UI. So I think ideal state is either a 2-way sync like Harness used to have for their CI/CD pipeline stuff OR simply managing specific things via Git and the APIs vs. other things in the UI.

For example – flag creation and properties in Git, but flag enablement in the UI so non-engineers can do that work.

Still working through what this might mean and other challenges it would bring up, so we don’t need to do it now.

But keeping engineers in their normal work area without having to give them direct access to the UI for edit purposes is appealing."