Hello & thank you for the Serverless Framework (I'm a big fan). I'm running sst in a development mode. Following lambda code outputs a folder structure from my OS. I would expect to see a lambda execution environment folder structure.

import {APIGatewayProxyEventV2, APIGatewayProxyHandlerV2} from "aws-lambda";
import * as fs from 'fs'

export const handler: APIGatewayProxyHandlerV2 = async (event: APIGatewayProxyEventV2) => {

    fs.readdirSync("/").forEach(file => {
        console.log(file);
    });

    return {
        statusCode: 200,
        headers: {"Content-Type": "text/plain"},
        body: `Response: ${JSON.stringify({})}`,
    };
};

I come across this when trying to use EFS in the lambda code. Attached code list my OS folder structure.  Any hints?

Yeah this one is tricky. The code is executing locally so it won't have access to the efs mount

thank you, where I can find more details how to mark function to not to execute locally ?

This can be used https://docs.serverless-stack.com/environment-variables#is_local

You can set this variable to false on your function: https://docs.serverless-stack.com/constructs/Function#enablelivedev

Hadn't spotted that one, @thdxr, nice

Recently added

ok that is interesting, thank you @thdxr and @Ross Coundon

@thdxr I think it might be possible to support EFS for live lambda dev? https://docs.aws.amazon.com/efs/latest/ug/efs-onpremises.html

@Frank low priority for me at the moment, I've decided to use S3 instead. Happy to help to test #739 once is done.

Sounds good! Thanks @Slawomir Stec