dave vader
dave vader
in the title https://go-vela.github.io/docs/reference/api/deployment/add/ custom parameters via the api is unclear but it exists in the swagger
## Description when executing a deployment its hard to keep track of which parameters were injected into a particular build we could keep track of them and display these clearly...
## Description when a repo has a lot of deployments historically, viewing them in the UI is cumbersome and slow.
## Description it can be frustrating debugging a deployment that is missing parameters, just to learn that the Add Deployment page is not clear that you have to click "Add"...
## Description easy to replicate, create a few deployments with various combinations of ref, task, target and parameters, send them, then go to Deployments and click "Redeploy" the fields should...
## Description see title, running local exec and sending a SIGTERM or a termination signal of some kind should run the cleanup, or at least try to. often times a...
## Description [kaniko docs](https://github.com/go-vela/vela-kaniko/blob/main/DOCS.md) are lacking a couple things: - available filepath arguments - how the parameters `tag` and `tags` differ ## Value clarity :)
## Description a commit message from github containing special characters will cause pipeline configuration to crash even though the pipeline does not inject the commit message into any fields example...
## Description would be useful to see the date + time in the deployments tab. this is just a rough example, see the "17 minutes ago": that could be exact...