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
When Kusion calls the module generators through RPC, the log information is being exposed to the output of the Kusion cmd, which needs to be removed.
What did you expect to happen?
The module RPC logs should not be exposed to the output of Kusion cmd.
How can we reproduce it (as minimally and precisely as possible)?
Execute the kusion build, kusion preview, kusion apply or kusion destroy cmd with Kusion module.
Anything else we need to know?
No response
Kusion version
$ kusion version
# paste output here
OS version
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
Install tools
The text was updated successfully, but these errors were encountered:
What happened?
When Kusion calls the module generators through RPC, the log information is being exposed to the output of the Kusion cmd, which needs to be removed.
What did you expect to happen?
The module RPC logs should not be exposed to the output of Kusion cmd.
How can we reproduce it (as minimally and precisely as possible)?
Execute the
kusion build
,kusion preview
,kusion apply
orkusion destroy
cmd with Kusion module.Anything else we need to know?
No response
Kusion version
OS version
Install tools
The text was updated successfully, but these errors were encountered: