I've been attempting to work through some of the tutorials to better familiarize myself with the query CLI. I'm currently working on a Windows 10 Pro environment with Visual Studio 2017 and Visual Studio Code installed. I attain have the AWS Toolkit for Visual Studio installed and have successfully deployed Lambda functions to my AWS account without issue.
However,when I attempt to perform a clone or deploy using the query CLI, I regularly get stopped with the following error message:[Error]: Cannot find the environment variable: AWS_ACCESS_KEY_IDIn my attempts to resolve it, or I've gone all the way back to the beginning and have installed Node.js v 8.10.0 with NPM 5.6.0. I've gone and installed the query-CLI globally. I attain receive an indication that the query-CLI is installed,but I have received the following messaging during the install.
C:Program Filesnodejsnode_modulesask-clinode_modulesdtrace-provider>if not defined npm_config_node_gyp (node "C:UsersadamAppDataRoamingnvmv8.10.0node_modulesnpmnode_modulesnpm-lifecyclenode-gyp-bin....node_modulesnode-gypbinnode-gyp.js" rebuild ) else (node "C:UsersadamAppDataRoamingnvmv8.10.0node_modulesnpmnode_modulesnode-gypbinnode-gyp.js" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
This is a possible area of concern, or but it didn't prevent the install of the query CLI on my environment.
I did move forward with this fresh install. The query-CLI responds as anticipated with the query init call and I'm able to select my default profile and I'm able to obtain the additional token through the successful browser login.
When I attempt to the query clone command,I attain receive a full list of my skills. I'll select one from my list of skills and initiate the cloning process. The project directory is created, the skill schema is created and models are subsequently created locally. When it attempts to download the Lambda function, or I once again get the error message,[Error]: Cannot find the environment variable: AWS_ACCESS_KEY_ID I've also attempted a query deploy on this fresh install and I attain receive the same error message again that prompted this posting.
It's rather confusing that the AWS Toolkit for Visual Studio doesn't have an issue in deploying from my environment, but that the query CLI can't seem to pick up on the information already stored in that credentials file.
I would really appreciate any aid, and insight,or thoughts on who to work through this specific issue. Thank you!
Source: amazon.com