How does ArgoCD's OCI source affect GitOps promoter?

[BenHesketh21]

I'm wondering if the community has had these discussions and what the general feel is for the future of GitOps promotions in general as well as specifically gitops-promoter.

In gitops-promoters case, it's focused on PRs being the 'vessel' for promotions so is there a way that OCI sources can work with this tool? Or is the only way for helm charts/kustomize artefacts to be stored in OCI and the hydrator render the final manifests which would then go through the PR workflow and using Got as the source as we are used to?

Just interested what the thoughts are on where the OCI world of GitOps fits into promotions? I personally think it makes things more difficult, in terms of visibility and auditing and that tools like gitops-promoter might have to pick up the slack on.

[zachaller]

The gitops-promoter is somewhat generic in that you just need a hydrator and an applier. In the case of OCI I could imagine doing something with that such as a custom applier that watches the "active" branch and say builds some OCI artifact and pushes it. I don't have much experience with OCI so con't go into exact details in how this would work but I could imagine something is possible