Lambda function examples should not have explicit names

[VenelinMartinov]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Related to pulumi/pulumi-terraform-bridge#1783

The basic example for lambda function has explicit name parameters: https://www.pulumi.com/registry/packages/aws/api-docs/lambda/function/#basic-example

This hurts code reuse and causes name clashes etc. It is also unnecessary since pulumi has auto-naming.

const iamForLambda = new aws.iam.Role("iam_for_lambda", {
    name: "iam_for_lambda",
    assumeRolePolicy: assumeRole.then(assumeRole => assumeRole.json),
});

can be

const iamForLambda = new aws.iam.Role("iam_for_lambda", {
    assumeRolePolicy: assumeRole.then(assumeRole => assumeRole.json),
});

and

const testLambda = new aws.lambda.Function("test_lambda", {
    code: new pulumi.asset.FileArchive("lambda_function_payload.zip"),
    name: "lambda_function_name",
    role: iamForLambda.arn,
    handler: "index.test",
    sourceCodeHash: lambda.then(lambda => lambda.outputBase64sha256),
    runtime: "nodejs18.x",
    environment: {
        variables: {
            foo: "bar",
        },
    },
});

can be

const testLambda = new aws.lambda.Function("test_lambda", {
    code: new pulumi.asset.FileArchive("lambda_function_payload.zip"),
    role: iamForLambda.arn,
    handler: "index.test",
    sourceCodeHash: lambda.then(lambda => lambda.outputBase64sha256),
    runtime: "nodejs18.x",
    environment: {
        variables: {
            foo: "bar",
        },
    },
});

Affected area/feature

[t0yv0]

I think this is exactly pulumi/pulumi-converter-terraform#122