Kethan sai

Hey @KuzonFyre , thank you for the information. Would you be open for a quick chat. I am available on discord, my handle is `ykethan`. Wanted to dive deeper into...

Hey @Zhuohui-Li, thank you for filing this, marking this as feature request. Note: tried overriding the property but was unable to modify the the property to v2 ``` resources.userPool.addPropertyOverride("LambdaConfig", {...

Hey 👋 thanks for raising this! marking this as feature request.

Hey @SebSchwartz, thank you for reaching. Could you try changing directory into `amplify/backend/function//`, remove the node_modules and running `pnpm i`, then at the root of the project run `amplify push`...

Hey @SebSchwartz, thank you for the information. Amplify CLI unfortunately does not handle symlinks well when it downloads and unzips your backend state (e.g. on `amplify pull`), which is a...

Closing the issue due to inactivity. Do reach out to us if you require any assistance.

Hey @OperationalFallacy, thank you for providing the app-id. On diving into the logs it appears the issue is occurring on the `amplify status -v`. To mitigate the issue i would...

Closing the issue due to inactivity. Do reach out to us if you require any assistance.

Hey @vikaskgahlawat, thank you for reaching out. From the following, Amplify CLI currently checks for version 6 .Net https://github.com/aws-amplify/amplify-cli/blob/cba0396bec4523f44c2814541e74204013ee8666/packages/amplify-dotnet-function-runtime-provider/src/utils/detect.ts#L24 Marking this as feature request

Hey @programad, thanks for reaching out. The `amplify/backend/function/` should contain a `amplify.state` file with the build command for the function. you can modify the build command to use a different...