Our future for easy rollback!

[peaceiris]

I believe we need a place to discuss the rollback experience in PipeCD, which is why I opened this discussion.

Currently, to perform a rollback after a deployment is completed, it is necessary to create a new deployment by reverting the manifest or creating a pull request to revert the Docker image tag. This process seems a bit cumbersome. I am convinced that PipeCD has the potential to make this flow clearer and simpler.

[khanhtc1202]

Thanks, @peaceiris. I understand your point 👍. Do you currently have any ideal process or flow in mind?
TBH, I think the current flow is a bit cumbersome, but it is clear. Please note that PipeCD is a GitOps tool, and it uses Git as its single source of trust, which means to PipeCD, each deployment should be a reflection of a manifest change commit. Happy to hear other opinions here cc @ffjlabo @t-kikuc

[peaceiris]

I think it would be convenient to be able to create a revert deployment triggered from a PipeCD application. For example, having a Revert button on the console page of a specific application, which, when clicked, makes the piped create a commit to revert the k8s manifest. Such a flow seems ideal.

[khanhtc1202]

It sounds nice 👍 I think this can be done easily since it looks similar to what we do for the EventWatch feature (I mean, we have a mechanism that allows piped to push/commit to the watching branch) 🤔

[peaceiris]

I agree with you. One concern I have is how PipeCD should manage the previous versions or commits.

[ffjlabo]

I agree with you. One concern I have is how PipeCD should manage the previous versions or commits.

PipeCD Application has information on the latest successful deployment, including the commit.

pipecd/pkg/model/application.pb.go

Lines 126 to 127 in b1177ab

	MostRecentlySuccessfulDeployment *ApplicationDeploymentReference `protobuf:"bytes,11,opt,name=most_recently_successful_deployment,json=mostRecentlySuccessfulDeployment,proto3" json:"most_recently_successful_deployment,omitempty"`
	// Basic information about the most recently trigered deployment.

So we might be able to create a revert commit and cancel the fix 🤔

[peaceiris]

That sounds good 😃

[peaceiris]

Input rollback target Artifact Version

I mentioned the future of the Revert button in the above thread. In addition, we can discuss a roll backing to a specific version.

If we want to roll back to a specific Docker image tag, it might be useful to input any artifact version from the web console and create an automatic commit by the piped for the rollback.