Feature Requests

Filters should allow for tags with branches not one or the other. It seems a pretty common use case to want only a branch to build but not run a deploy workflow unless branch:v1.0 tag has been added/approved/merged etc. CCI-I-305

Provide automation for blue/green releases. Validation of a release would be based on a set of one or more user specified SLOs The failure to meet any one of the defined SLOs would cause the release to be immediately rolled back Rollbacks could trigger a CCI pipeline and/or call a user specified webhook or webhooks

This would include features like: Tracking current deployment versions in production Automated rollbacks in cases of failures Audit trails / logging Various deployment paradigms like Blue/Green deployments, Tracking metrics like MTTR, change failure rate, etc. CCI-I-1350

CF has an out of the box ArgoCD integration that makes things like Canary deploys to k8s very simple. https://codefresh.io/docs/docs/integrations/argo-cd/