You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Toolkit currently is using the same sam build folder to sam cli, .aws-sam. Toolkit should use a separate folder, say .aws-toolkit for the target build folder to avoid potential conflict issues.
This is blocked by sam cli issue since sam cli copies all the folder structure from the lambda base directory to the target build directory. If the lambda base directory is the same to the module root, it copies the toolkit build folder recursively to itself.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Toolkit currently is using the same sam build folder to sam cli,
.aws-sam
. Toolkit should use a separate folder, say.aws-toolkit
for the target build folder to avoid potential conflict issues.This is blocked by sam cli issue since sam cli copies all the folder structure from the lambda base directory to the target build directory. If the lambda base directory is the same to the module root, it copies the toolkit build folder recursively to itself.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: