Hello! Quick question working with Pulumi on Windo...
# general
p
Hello! Quick question working with Pulumi on Windows. Often, when I hit an Unknown error deploying my stack, my cmd window will hang on the deploy. Sending a ctrl C doesn't give me the input control back on my CMD window, I always need to close it and open a new one. I am able to debug my Unknown error using the verbose mode and dumping the logs to a txt file, and I also see that when I do ctrl C, it closes grpc client, but won't let me use my cmd window again. I tried powershell and also running in admin mode, but nothing helped. What would you suggest to try and find why this is doing this ?
An example of a miss configuration on a bucket that cause my CMD window to hang on the deploy. Grabbed this from the logs and fixed it, but trying to understand why it makes my CMD window hang even after I CTRL+C
Copy code
I0828 12:05:51.034383   38540 step_executor.go:516] StepExecutor worker(41): step create on urn:pulumi:local::mystack::aws:s3/bucketReplicationConfig:BucketReplicationConfig::replication failed with an error: 1 error occurred:
	* creating S3 Bucket (tf-test-bucket-source-12345tr74h38t74gh3) Replication Configuration: operation error S3: PutBucketReplication, https response error StatusCode: 400, RequestID: 3T6HWQ0SRZJWK0HP, HostID: -------------------------------------=, api error InvalidRequest: DeleteMarkerReplication cannot be used for this version of Cross Region Replication configuration schema. Please refer to S3 Developer Guide for more information.