"Building" Task Commands
It would be a better user experience if users could configure task commands using a simple, building-block approach. For example, a user could select “Tofu import” and only need to enter the resource address. This would also make it easier to write policies based on these commands.
- Problem
Log in to comment and vote
Comments1
Jonah Kowall
Nov 11
Thanks Vincent. There are two asks here and I'd treat them differently.
Policies for tasks is the one I want to dig into. Approval policies already run against tasks and see the command, so "allow tofu import, require approval for anything else" works today. The catch is that you are matching on a raw command string, which is brittle. If you share two or three rules you are trying to write, we can tell whether that covers it or whether tasks need to expose more structured data to policy.
On the command builder, I don't think a catalog of pre-built commands is where we'd go. We would have to maintain it per tool and subcommand, and tasks are meant to stay an open-ended command. There is a related request for saved commands and a command picker, worth a vote if that is closer to what you need: https://feedback.spacelift.io/p/ask-favoritesbookmarks-vendor-aware-command-picker-in-tasks
I'm leaving this open for votes so others can add their task policy cases.