Closed alexander-medvedev closed 1 month ago
Hi @alexander-medvedev ,
I can see that StartDirectoryListingCommand
was added 3 weeks ago. Since you mentioned you are running this from Lambda, my guess is that you are using the SDK provided through Lambda itself. The Lambda provided SDK only gets updated a handful of times per year, the last time being a few months ago.
In order to access the most up to date SDK version with the changes you are after you need to provide your own SDK.
Thanks, Ran~
This issue has not received a response in 1 week. If you still think there is a problem, please leave a comment to avoid the issue from automatically closing.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.
Checkboxes for prior research
Describe the bug
StartDirectoryListingCommand does not exist in AWS Transfer SDK
The next code fails with "StartDirectoryListingCommand is not a constructor;" error
import pkg from '@aws-sdk/client-transfer'; const { TransferClient, StartDirectoryListingCommand } = pkg; const command = new StartDirectoryListingCommand(input);
after printing out pkg I found that the getter is missing: ... SendWorkflowStepStateCommand: [Getter], ServiceUnavailableException: [Getter], SetStatOption: [Getter], SftpAuthenticationMethods: [Getter], SigningAlg: [Getter], // StartDirectoryListingCommand should be here StartFileTransferCommand: [Getter], StartServerCommand: [Getter], State: [Getter], StopServerCommand: [Getter], ...
SDK version number
@aws-sdk/client-transfer
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
20.x (running on AWS Lambda)
Reproduction Steps
import pkg from '@aws-sdk/client-transfer'; const { TransferClient, StartDirectoryListingCommand } = pkg; const command = new StartDirectoryListingCommand(input);
Observed Behavior
StartDirectoryListingCommand is not a constructor
Expected Behavior
command is created
Possible Solution
No response
Additional Information/Context
executed on AWS Lambda (nodejs20.x)