Currently, we are not able to get logs from executed Actions via Capact CLI. As a result, user needs to use the kubectl and get a proper pods names.
We can distinguish between two options:
get the latest logs from the Action execution
stream logs from the Action execution
The first one can be already implemented, where for the second one it will be good to use the websockets. Unfortunately, we don't support it yet.
Reason
Requires installation of external tools (kubectl and configure it with proper cluster) for some of our examples. This should be simplified and Capact CLI should be the only one which is needed. One 💍 to rule them all 😎 . Same as we did for #328 and #466.
Use cases
System User - with Capact CLI can easily get the Action logs. Currently, it involves usage of external CLIs and manual discovery of related pods.
Description
Currently, we are not able to get logs from executed Actions via Capact CLI. As a result, user needs to use the
kubectland get a proper pods names.We can distinguish between two options:
The first one can be already implemented, where for the second one it will be good to use the websockets. Unfortunately, we don't support it yet.
Reason
Requires installation of external tools (kubectl and configure it with proper cluster) for some of our examples. This should be simplified and Capact CLI should be the only one which is needed. One 💍 to rule them all 😎 . Same as we did for #328 and #466.
Use cases