You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 29, 2023. It is now read-only.
The output of kdt deploy is famously large, and people aren't able to locate actual errors which happen amongst all the noise. A lot of it is due to the fact that the imported Shopify deploy code is very verbose as well.
Proposing the following behavior:
If deploy succeeds, we should just print the number of kubectl artifacts which were successfully applied and exit silently.
If deploy does not succeed, only the last failing operation's command name and output values should be printed. Additionally, the specific file name inside the artifact which failed should be preserved (it currently isn't.)
In both cases we could just show a progress bar of the number of kubectl / deploy operations compared to the total. The output could also be simpler if stdout is not a tty.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Migrated from pre-OSS repository
The output of
kdt deploy
is famously large, and people aren't able to locate actual errors which happen amongst all the noise. A lot of it is due to the fact that the imported Shopify deploy code is very verbose as well.Proposing the following behavior:
In both cases we could just show a progress bar of the number of kubectl / deploy operations compared to the total. The output could also be simpler if stdout is not a tty.
The text was updated successfully, but these errors were encountered: