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
Terraform v1.3.3
on linux_amd64
+ provider registry.terraform.io/hashicorp/null v3.2.0
Use Cases
I find the echoing of the command that local-exec will execute to be entirely too verbose. The output from even relatively simple examples can be hard to parse. Medium- to high-complexity examples are overwhelming.
Plan: 1 to add, 0 to change, 0 to destroy.
null_resource.test: Creating...
null_resource.test: Provisioning with 'local-exec'...
null_resource.test (local-exec):Executing: ["/bin/sh" "-c" " echo {\"competitor\":\"Cogswell Cogs\",\"name\":\"Spacely Space Sprockets\"}\n"]
null_resource.test (local-exec):{competitor:Cogswell Cogs,name:Spacely Space Sprockets}
null_resource.test: Creation complete after 0s [id=5577006791947779410]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The "Executing:" output is completely unnecessary.
Attempted Solutions
None. I don't see a way to suppress this.
Proposal
Provide a quiet parameter to local-exec. By default it is false indicating that local-exec should output the command about to be executed (i.e. the behavior remains as it is today). If it is true, the Executing: ... output will be supressed.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Terraform Version
Use Cases
I find the echoing of the command that local-exec will execute to be entirely too verbose. The output from even relatively simple examples can be hard to parse. Medium- to high-complexity examples are overwhelming.
Produces this output --
The "Executing:" output is completely unnecessary.
Attempted Solutions
None. I don't see a way to suppress this.
Proposal
Provide a
quiet
parameter to local-exec. By default it isfalse
indicating that local-exec should output the command about to be executed (i.e. the behavior remains as it is today). If it is true, theExecuting: ...
output will be supressed.Produces this output --
References
No response
The text was updated successfully, but these errors were encountered: