PATCH 0044-Allow-creating-lambdas-without-code-related-properti.patch

[t0yv0]

Reverts a bridge bug temporarily.

[t0yv0]

Per #3959 this creates friction in routine upstrem upgrades. Digging up some more information here.

[t0yv0]

This has the back-history here: #3420

When importing lambdas, we run afoul of ExactlyOneOf due to a bridge issue, so the patch replaces that with ConflictsWith.

[t0yv0]

It looks really like a good example of pulumi/pulumi-terraform-bridge#1949

This is harder to automatically fix in the bridge.. It is indeed something that needs lambda-specific thought. We cannot plausibly manufacture a value here:

│ Error: Invalid combination of arguments
│
│   with aws_lambda_function.test_lambda,
│   on generated.tf line 4:
│   (source code not available)
│
│ "filename": one of `filename,image_uri,s3_bucket` must be specified
╵
╷
│ Error: Invalid combination of arguments
│
│   with aws_lambda_function.test_lambda,
│   on generated.tf line 7:
│   (source code not available)
│
│ "image_uri": one of `filename,image_uri,s3_bucket` must be specified
╵
╷
│ Error: Invalid combination of arguments
│
│   with aws_lambda_function.test_lambda,
│   on generated.tf line 16:
│   (source code not available)
│
│ "s3_bucket": one of `filename,image_uri,s3_bucket` must be specified

I think once we figure out a good answer to #3376 we can also revisit this patch.

[VenelinMartinov]

Two regression tests which are relevant here: TestSourceCodeHashImportedLambdaChecksCleanly and TestUpdateImportedLambda