This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hello guys, our release action failed recently due to the following error.

GoReleaser latest installed successfully
/opt/hostedtoolcache/goreleaser-action/2.2.0/x64/goreleaser -p 3 release --rm-dist
  ⨯ command failed                                   error=unknown flag: --rm-dist
Error: The process '/opt/hostedtoolcache/goreleaser-action/2.2.0/x64/goreleaser' failed with exit code 1

You can find the error in detail here. https://github.com/pulumiverse/pulumi-cpln/actions/runs/10706583306/job/29684717209 I believe the error is related to the args found in the

release.yml

file. https://github.com/pulumiverse/pulumi-cpln/blob/main/.github/workflows/release.yml#L62 Is the solution to remove the

--rm-dist

or should we just use

goreleaser/goreleaser-action@v5

and update the workflow as necessary?

Hey folks - one of my colleague facing the issue, did someone face it before\has recommendations? Hello! Quick question working with Pulumi on Windows corp laptop. 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 (and do a few commands with isengardcli + pulumi stack login before I can start working again with pulumi). 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 ? (edited) 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

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.

pulumi_aws==6.50.1
pulumi==3.130.0

Hey guys, opening this to a little discussion, what are some of the tradeoffs that you consider when deciding to create a Pulumi-backed IAM Policy Document via ONE of the following mechanisms: 1. Invoking aws.iam.getPolicyDocument (function approach) 2. Assigning a variable of type aws.iam.PolicyDocument (interface approach) 3. JSON.stringify approach e.g. (raw approach, inline or file, etc.)

import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";

const policy = new aws.iam.Policy("policy", {
    name: "test_policy",
    path: "/",
    description: "My test policy",
    policy: JSON.stringify({
        Version: "2012-10-17",
        Statement: [{
            Action: ["ec2:Describe*"],
            Effect: "Allow",
            Resource: "*",
        }],
    }),
});

I'm also interested on how you guys are approach authoring them too, so if you have any unique practices, I'm interested to see!