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

<@UE1LN7A22> Would you have any idea on how we can get this?

Sorry, I haven't used the Go libs myself, so I'm not sure. <@UBAJ7TD53>?

<@UB3BGTV63> Still waiting for some feedback on this.

<@UE1LN7A22> <@UEEUJNR9B> I am not fully up to date on the Go stuff. <@UB3BGTV63> who owns this? <@UB27BHS4B>?

I would appreciate help in resolving this.

We are building stuff based on pulumi and this is a blocker for us.

<@UEEUJNR9B> <https://pulumi.io/reference/pkg/nodejs/@pulumi/gcp/serviceAccount/#Key-pgpKey>

I _think_ it should be a base64-encoded string

So we cannot generate a user profile without a PGP key?

I saw the code and AFAIK it is not possible

<@UEEUJNR9B> yes, it is correct that you must provide a PGP key, unfortunately.

I knew that. But wanted to be sure. That brings complexity like `keybase`

I know, that’s why I was confirming :smile:

I’m checkout out why it’s required now

Our AWS provider uses the Terraform AWS provider to do resource CRUD operations, and Terraform requires the `pgp_key` field to be set: <https://github.com/terraform-providers/terraform-provider-aws/blob/f42c7c018da40cc33377c4b6c66a75d5f41ad2ca/aws/resource_aws_iam_user_login_profile.go#L30-L33>

<@UEEUJNR9B> Most people don’t administrate users or user logins from infrastructure-as-code platforms. Typically you’d create IAM groups and roles, and then create user accounts and logins from the console.

There are many reasons for this, but the main ones are that it becomes a lot easier to leak credentials and creates chicken-and-egg problems like: should users manage their own passwords in the code, etc.

FWIW - the request to not require PGP for this API is in tracked in <https://github.com/terraform-providers/terraform-provider-aws/issues/4564>.