is there a way to publish the lambda with different aws-lambda-tools-xxx.json for different environment (prod, staging, dev)?

[xiaohui-hiwintech]

We have three environments (prod, staging, dev), is there a way that we can use different aws-lambda-tools-xxx.json to publish to different environments in VS2022? If not, is there any other way we can achieve this goal? thank you so much.

[ashishdhingra]

@xiaohui-gsv I do not think you could use different aws-lambda-tools.default.json per environment? However, the AWS Extensions for .NET CLI tooling supports --config-file command line switch to override the default config file (refer aws/aws-extensions-for-dotnet-cli#54 (comment)).

I came across the link #126 (comment) that might be helpful.

[xiaohui-hiwintech]

Cool, thank you so much, it works by using the dotnet lambda deploy-function --config-file aws-lambda-tools.xxxx.json, thank you so much.