Lambda Sync no longer works in VS Code (had to revert to v3.27.0

[hideflolife]

Trying to do a Lambda Sync (i.e., Sync SAM Application (formerly Deploy)) failed with the following output:

2024-11-01 13:10:06.415 [info] Command: (not started) [C:\Program Files\Amazon\AWSSAMCLI\bin\sam.cmd sync --template .\template.yaml --s3-bucket [buckeName] --stack-name [this was empty, i.e., ""] --region us-east-1 --no-dependency-layer --no-watch] (running processes: 0)
2024-11-01 13:10:08.243 [error] aws.samcli.sync: Error: Failed to sync SAM application (deployType: infra; skipDependencyLayer: true; region: us-east-1; template: [object Object]; paramsSource: 2; stackName: [stackName]; bucketName: [bucketName]; syncFlags: []; projectRoot: file:///e%3A/OneDrive/[source root])
	 -> Error: sam sync exited with a non-zero exit code: 2 [NonZeroExitCode]
	 -> UnknownError: undefined

I did notice that the latest version asked for additional information related to parameters and gave me a warning on a missing samconfig.toml file

Reverting back to v3.2.7 allowed me to successfully sync.

[justinmk3]

This may have been fixed by #5913

Would you be able to try the prerelease build? https://github.com/aws/aws-toolkit-vscode/releases/tag/prerelease (Just download the vsix file and run Extensions: Install from VSIX... from the vscode command palette)

[vicheey]

@hideflolife, could you please provide detail steps to reproduce the bug?

1. From where do you initiate the sync command?
2. What options did you choose for all the prompters?
3. Do you have samconfig.toml in your project folder?

[justinmk3]

@vicheey just for reference, note the --stack-name [this was empty, i.e., ""] part of the command.

[vicheey]

There are 4 various entry points where the sync command can be triggered from:

1. Command palette
2. Resource node in Explorer section under a specific region (like in the screenshot above)
3. Application Builder section resource node (deploy icon)
4. Context menu when right click on template.yaml
   Knowing from where the command was trigger and the input into the prompters would help with reproducing the bug to understand why empty stack name was pass to the sync command.

[hideflolife]

As shown in the image I uploaded, I go to the AWS extension menu, right-click on Lambda, then select the Sync SAM Application option, to initiate the upload of the altered Lambda code.

Once clicked, the "wizard" asks for the optional parameters, e.g., the template file, the S3 bucket, etc.. I note that in the working version v3.2.7, it asked for 3 parameters. The most recent version appears to ask for more.

I didn't have a samconfig.toml previously - is this now needed?

[seshubaws]

Hello @hideflolife , I am trying to repro this.

Once clicked, the "wizard" asks for the optional parameters, e.g., the template file, the S3 bucket, etc.. I note that in the working version v3.2.7, it asked for 3 parameters. The most recent version appears to ask for more.

I saw in the logs you posted, it says --stack-name [this was empty, i.e., ""] does this mean you did not pass in a stack name?

I didn't have a samconfig.toml previously - is this now needed?

No, you shouldn't need samconfig.toml now either.

I was able to go to the AWS extension menu in the Explorer section, right-click on "Lambda", then select the Sync SAM Application option, and upload altered Lambda code to a stack without a samconfig.toml, so I am not able to repro atm. Could you please help to provide more details on what you entered into the wizard prompter when you initiated the sync?

[hideflolife]

Using v3.27.0, which works to allow syncing of my Lambda app, I use the following procedure:

• Navigate to the AWS logo on the far right icon toolbar
• Right-click on the Lambda option and select 'Sync SAM Application (formerly Deploy)'
• When asked about 'Select a SAM template.yaml file', I select my 'template.yaml' file
• When asked about 'Select a stack (or enter a name to create one)', I select my previously created stack
• When asked about 'Select a bucket (or enter a name to create one)', I select my previously created bucket
• The application builds and syncs my Lambda application
• I'm happy

Using v3.32.0, which works to allow syncing of my Lambda app, I use the following procedure:

• Navigate to the AWS logo on the far right icon toolbar
• Right-click on the Lambda option and select 'Sync SAM Application (formerly Deploy)'
• When asked about 'Select a SAM template.yaml file', I select my 'template.yaml' file
• When asked about 'Specify required parameters and save as defaults', I don't enter any and press enter
• When asked about 'Select a stack (or enter a name to create one)', I select my previously created stack
• When asked about 'Select a bucket (or enter a name to create one)', I select my previously created bucket
• When asked about 'Press enter to proceed with highlighted option', by default 'Watch' and 'Save parameters' are selected - it doesn't seem to matter what I select or don't select, I press enter
• The application fails to build
• I'm sad

[vicheey]

Thank you for your information, @hideflolife.
While I am looking into the issue, I would like to introduce the recent update with v3.32+ version. You can choose deploy/sync your application directly from Application Builder with fewer clicks.

We would you to give it a try and see if the problem persists with entry point as well while we work on the fix.

[vicheey]

I failed to reproduce with issue. Please upvote this issue if this becomes a persistent failure.

[seshubaws]

@hideflolife could you please give us more info about the VSCode version you're using, and also your machine architecture info?

[hideflolife]