Getting a weird issue trying to incorporate a python lambda in our nodejs project in AWS, does anyone have any idea what I can do to fix this besides just manually setting all of the runtimes and removing the runtime from the Pulumi.yaml file? It seems weird the yaml for the whole project overrides the actual setting for the lambda. When I create the Python lambdas the runtime I pick is over-ridden by the runtime in the Pulumi.yaml, so instead of running in Python 3.8, it runs in NodeJS 14.x which breaks the lambda unless I manually change it in AWS Management Console. This is the Pulumi Code:

export const onDocumentsIndexingEvent = new lambda.Function(`onDocumentsIndexingEvent-${stack}-${project}`, {
    code: new pulumi.asset.AssetArchive({ '.': new pulumi.asset.FileArchive('./jobs/python/mb_indexer_gpt/') }),
    runtime: lambda.Runtime.Python3d8,
    timeout: 200,
    layers: [pythonLayer.arn],
    handler: 'mb_indexer.lambda_handler',
    role: pythonLambdaRole.arn,
    environment: {
        variables: {
            OPENAI_API_KEY: ''
        }
    }
})

do you have a typo there for

runtime

?

I can try the enum, I also did ‘python3.8’ as a string. Yes, I am using Typescript in the project, and it seems correct to me. I will try with --refresh

It will keep doing that every time it detects the runtime has been changed from what it wants to set

“runtime”: “nodejs14.x”,

"inputs": {
                    "__defaults": [
                        "memorySize",
                        "name",
                        "packageType",
                        "publish",
                        "reservedConcurrentExecutions",
                        "skipDestroy"
                    ],
                    "code": {
                        "4dabf18193072939515e22adb298388d": "0def7320c3a5731c473e5ecbe6d01bc7",
                        "assets": {
                            ".": {
                                "4dabf18193072939515e22adb298388d": "0def7320c3a5731c473e5ecbe6d01bc7",
                                "hash": "76557255a1b978ea5f4df5c201cb6a1bd1aa6b7b2f218bb232debd1b137425b7",
                                "path": "./jobs/python/mb_indexer_gpt/"
                            }
                        },
                        "hash": "76557255a1b978ea5f4df5c201cb6a1bd1aa6b7b2f218bb232debd1b137425b7"
                    },
                    "environment": {
                        "__defaults": [],
                        "variables": {
                            "OPENAI_API_KEY": "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",
                            "__defaults": []
                        }
                    },
                    "handler": "mb_indexer.lambda_handler",
                    "layers": [
                        "arn:aws:lambda:us-west-2:617706700270:layer:python_layer:7"
                    ],
                    "memorySize": 128,
                    "name": "onDocumentsIndexingEvent-ai-smart_onboarding-3075219",
                    "packageType": "Zip",
                    "publish": false,
                    "reservedConcurrentExecutions": -1,
                    "role": "arn:aws:iam::617706700270:role/pythonLambdaRole-ai-smart_onboarding-4552f77",
                    "runtime": "nodejs14.x",
                    "skipDestroy": false,
                    "timeout": 200
                }

That’s no good, what if you try changing the runtime to some static string that makes no sense - just to ensure that an error occurs

I tried it with a random static string and the pulumi up --refresh command. It resulted in the exact same thing as when I did the string

'python3.8'

or

lambda.Runtime.Python3d8