Bob Rohan

I believe in your example, you may have reduced the effectiveness of Flux by introducing additional overhead, or risk, or both - depending on what your strategy is for promotion....

I think the short answer is nothing relevant, but I'll include some detail incase you're driving at a point I don't yet understand. In the fleet repo, both staging and...

Yes, I think I can see how that would work for the example above. We have multiple policies in some clusters, but by refactoring the image automation CRDs from flux-system...

Been a bit of a day going back and forth on this one. Main fumble point seems to be around what namespace various components logically reside within, Secret (for git),...

Yes, well, sort of. We dump the flux bootstrap results out to disk and store in git for bootstrapping via terraform initiated custom ECS task. Gives us a sensible way...

Yep, fair point. The upgrade did get me past that issue thanks. After many more refactoring, can confirm while your suggestion is very useful for those looking to run a...

I don't @timja , I not longer have access for the client where this work was done. I'll reach out see if someone could pick this up

> It's not clear from the redacted part if the error "not found" is reported about the parent repo (inaccurately The error redacted reports about the parent repo > I...

Found some old PRs with context defined as `atlantis/apply: /` Therefore where the workspace is the same as path, the path limit is 119 characters.

NB whitespace replaced with + was also not intuative, found this on some go forum and happened to work. But can't workaround the colon issue