No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

does setting `on_output` conflict with other logging properties like `log_verbosity` ?

```Traceback (most recent call last):
  File "/home/app/index.py", line 273, in handler
    deploy_cloudfront(app_id, base_domain, event_detail, bucket_name)
  File "/home/app/index.py", line 69, in deploy_cloudfront
    raise e
  File "/home/app/index.py", line 63, in deploy_cloudfront
    stack.up(on_output=print, log_verbosity=9, log_to_std_err=True, debug=True)
  File "/home/app/pulumi/automation/_stack.py", line 308, in up
    up_result = self._run_pulumi_cmd_sync(args, on_output)
  File "/home/app/pulumi/automation/_stack.py", line 747, in _run_pulumi_cmd_sync
    result = _run_pulumi_cmd(args, self.workspace.work_dir, envs, on_output)
  File "/home/app/pulumi/automation/_cmd.py", line 55, in _run_pulumi_cmd
    with subprocess.Popen(
  File "/usr/local/lib/python3.9/subprocess.py", line 951, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/local/lib/python3.9/subprocess.py", line 1754, in _execute_child
    self.pid = _posixsubprocess.fork_exec(
TypeError: expected str, bytes or os.PathLike object, not int```

`TypeError: expected str, bytes or os.PathLike object, not int` the only int provided is the `log_verbosity` prop that per the docs say it is an int? <https://www.pulumi.com/docs/reference/pkg/python/pulumi/#module-pulumi.automation>

yes, it worked by setting the `log_verbosity` to a string even though the docs say int

the docs or automation api itself should be updated for the `log_verbosity` prop value type it expects