sam commands in codecatalyst dev env may fail if they inherit the local setting #4640
Labels
bug
We can reproduce the issue and confirmed it is a bug.
remote-execute
SSM, remote-ssh, CodeCatalyst dev env
sam
service:codecatalyst
settings
Problem
sam cli commands fail in codecatalyst remote dev envs if the
aws.samcli.location
setting is set in "user" settings (i.e. on the local machine).Steps to reproduce the issue
aws.samcli.location
to something on the local vscode settings (aka "User" settings)./usr/local/bin/sam
AWS: Create Lambda SAM Application
commandExpected behavior
When running in a remote context (vscode remote-ssh), sam functionality in the Toolkit should ignore the "User" scoped
aws.samcli.location
setting inherited from the local machine. Because the local machine path is usually not valid for a remote machine.Proposal
aws.samcli.location
with a different scope?aws.samcli.location
inherited from "User"/Global scope.The text was updated successfully, but these errors were encountered: