Spacectl Deploy and Logs Enhancement
In an effort to make Spacectl more CI friendly, it’ll be useful to have the following features.
With
spacectl stack deploy --tailcommand, it’ll be useful to optionally have spacectl exit cleanly IF the tail hits anUNCONFIRMEDstate.With
spacectl stack log --tailcommand, it’ll be useful to optionally have spacectl exit cleanly IF the tail hits anUNCONFIRMEDstate.With
spacectl stack deploycommand, it’ll be useful to optionally have spacectl only return the run ID
The above requested features have workarounds in my process such as using grep for output filtering and subshell execution for looping through tails for better control, but the process could be improved and handle errors much better if the above was added.
- Problem
Log in to comment and vote
Comments1
Black Breeze
Jan 29
Thanks for taking the time to propose this @Ernesto Huizar . I see where you’re coming from but I think implementing it would complicate the API of the CLI to a point where you’d have easier time just hacking something in your favorite shell than learning and wrangling
spacectlconfig/flags to do exactly what you wanted it to do. Let’s face it - anyone capable of doing that can also reliably produce a Bash one-liner. I’ll stick to Unix philosophy here.