Khanh Tran
Khanh Tran
The current field path only supports parse path index (number) to access object/element of an array by number (ref: [code](https://github.com/goccy/go-yaml/blob/master/path.go#L47-L54)). In some case, it would be nice if we can...
**What would you like to be added**: Currently, we only support login to Helm chart registry using basic authentication, but it would be nice if other methods could be used...
**What would you like to be added**: Just like Helm or Kustomize but instead of only specify the version, which external binary should be installed will be configured via piped...
**What would you like to be added**: Currently we have a way to remotely upgrade version of the piped (agent), would be nice if we can also restart the piped...
**What would you like to be added**: Support deploy standalone ECS task **Why is this needed**: Currently, PipeCD only supports running ECS tasks handled by ECS service. In some cases,...
**What would you like to be added**: Currently, the PipeCD eventwatcher value replacement only supports value under a simple query path like `$.spec.xyz[1].yy...` (only index and key name allowed). It...
**What happened**: When the deployment of kind k8s got errors (because of kubectl version mismatch - for instance), the ROLLBACK stage will be started. If the ROLLBACK is failed as...
**What would you like to be added**: This error is shown in the stage log. Need to found out and update error format for all error like this ``` (%!w(*fmt.wrapError=&{failed...
**What would you like to be added**: Currently, on adding application (via suggestion or manual) we don't fetch the application `spec.description` information in `app.pipecd.yaml` file. So, even we have prepared...
**What happened**: In case of adding application via manual adding form, even we have `spec.labels` value in the `app.pipecd.yaml` file, those labels values are not reflected to the application UI...