Add a new field to show why command was failed.

[pipecd-bot]

pipecd/pkg/model/command.pb.go

Lines 163 to 166 in 48dcb9b

	HandledAt int64 `protobuf:"varint,22,opt,name=handled_at,json=handledAt,proto3" json:"handled_at,omitempty"` // TODO: Add a new field to show why command was failed.
	Type Command_Type `protobuf:"varint,30,opt,name=type,proto3,enum=model.Command_Type" json:"type,omitempty"`
	SyncApplication *Command_SyncApplication `protobuf:"bytes,31,opt,name=sync_application,json=syncApplication,proto3" json:"sync_application,omitempty"`
	UpdateApplicationConfig *Command_UpdateApplicationConfig `protobuf:"bytes,32,opt,name=update_application_config,json=updateApplicationConfig,proto3" json:"update_application_config,omitempty"`

This was created by todo plugin since "TODO:" was found in 48dcb9b when #3342 was merged. cc: @nghialv.

[t-kikuc]

Before starting this task, please provide a to-do list here.
Just adding the field is not enough.

For example, where to set the reason value, how to show it to users, ...

[Bibisha06]

hey @t-kikuc i would like to work on this issue, I have provided a to-do list. please confirm if i can move ahead with this approach

1. Update Protobufs

• Add string handled_reason to Command (pkg/model/command.proto).
• Add string handled_reason to ReportCommandHandledRequest (pkg/app/server/service/pipedservice/service.proto).
• Regenerate the .pb.go files.

2. Pass the Error in the Agent

• Create a new helper path in the piped command reporting layer (pkg/app/piped/apistore/commandstore/store.go) to send the reason for failed commands without impacting success flows.
• Update failure paths in the command handlers (pkg/app/piped/... such as planpreview, scheduler, etc.) to pass err.Error() when reporting COMMAND_STATUS_FAILURE.

3. Save the Error in the Server Datastore

• Update ReportCommandHandled in pkg/app/server/grpcapi/piped_api.go to capture HandledReason from the gRPC request.
• Update commandStore.UpdateCommandHandled(...) and related datastore logic to properly persist handled_reason into the Command model in the database.

4. User UI

• pipectl CLI: Update command watchers/output to print the failure reason when a command fails.
• Web UI: Trigger an error toast notification containing the calculated failure message if the command status registers as failed.