I did the following "ask deploy":
RI-mac:multiple-streams egilchri$ ask deploy
-------------------- Create Skill Project --------------------
Profile for the deployment: [default]
Skill Id: amzn1.ask.skill.cdb74c79-59a5-4e01-adb2-cad787040dd9
Skill deployment finished.
Model deployment finished.
Create Lambda error.
InvalidParameterValueException: The runtime parameter of nodejs6.10 is
no longer supported for creating or updating AWS Lambda functions. We
recommend you use the new runtime (nodejs10.x) while creating or
updating functions.
Can someone tell me how to fix this?
I think I figured it out. I haven't used this in a while. Updgrading ask cli seemed to do the trick.
On MacOS
sudo npm install -g ask-cli
Related
I've followed Codeship's custom script deployment pipeline setup but reached trouble with the following error when trying to deploy to Google App Engine:
pyenv: python2: command not found
Here are screenshots of my codeship setup commands:
The deployment pipeline setup:
and the Codeship console output:
Any ideas why it thinks I'm on python2?
The fastest way to reach CodeShip support is by emailing support#codeship.com - You'll need to set the python version to 2.7 before the deploy steps in order to use this deploy script.
We can continue to work on the ticket created with support - but I wanted to be sure to answer here for any other users. :)
Combining the answers from #Michelle and #eespinola, I had to change from:
pyenv local 3.7
to:
pyenv global 2.7 3.7
in the setup commands
I want to automate my chatbot by botium. But not clear how to integrate it with selenium to test its button and conversational flow. Also, want to setup webdriverio connector and how to write its script. Can anyone provide a proper demo for this?
This is a rather vague question. You can find introduction tutorial in the Botium Wiki.
And here is a tutorial how to start your own Selenium server and connect it to Botium Box.
Welcome to StackOverflow Shubham!
I'll try to guide you as best I can, but note that StackOverflow is usually a place to debug a current programming issue you are facing, not a place to seek start-up advice. Read this article and try to create a reproducible example next time.
WebdriverIO has stellar documentation! I'd start by reading the Getting Started section. Go through all the sections, including the initial setup, so you get more comfortable.
Install a WebdriverIO Boilerplate Project of your liking and run your first tests.
Example:
Let's say I want to run some Mobile tests cross-browser. That means Appium, so I'm looking at webdriverio/appium-boilerplate project
Read the README.md file! (you ever cooked without reading the recipe first?! Me neither!)
Clone the project: git clone git#github.com:webdriverio/appium-boilerplate.git
Install software dependencies: npm install (or w/e other package manager you're using...)
Run the test command: npm run-script <testScript> (in our case, npm run ios.sauce.rdc.app for npm run ios.sauce.rdc.app for Android)
Make use of the online resources available! There are a lot of great WebdriverIO tutorials & articles creators out there. You have to find them! I personally recommend you watch all the WebdriverIO video tutorials created by Kevin Lamping. I you like Kevin's knowledgeable & friendly delivery, consider enrolling for one of his online WebdriverIO courses.
Seek help when you're lost! There's a very friendly & helpful community building up behind WebdriverIO. Tap into that resource! Use the WebdriverIO Gitter Chat channel to find more help.
After setting up the boilerplate project, I'd start by writing the most basic Botium test: use the Botium API, or some Selenium commands to generate some messages, then assert the outcome & the bot's answers. Pretty straightforward. Break it down, step by step. Hope you make it work!
!Note: A boilerplate project is a project baseline, basically the minimal configuration to produce a running test framework. You can read more about boilerplate projects here.
I have been building an app with awsamplify for quite some time now. Today I descided to run some test and when I did
npm run start-web
Everythin worked fine. Now I went on to run mobile test with the use of Expo and ran
npm run ios & npm run android
which both returned the following errors.
Unable to resolve "./aws-exports" from "App.js"
Building JavaScript bundle: error
my problem is similar to the one below just its amplify and not awsmobile
https://github.com/aws-amplify/amplify-js/issues/669
Deos anyone know what I can do to resolve this?
Thanks alot!
I jsut removed some unused imports and the error changed to this
Unable to resolve "#aws-amplify/ui/dist/style.css" from "node_modules\aws-amplify-react\dist\Amplify-UI\Amplify-UI-Components-React.js"
Barely mentioned in the AWS docs:
For setting up a local dev folder, from an existing amplify repo, use an amplify env pull,
It will "pull" the ./aws-exports.js from the server, the latest one that was pushed there,
similar to git push and git pull but for the amplify env
It's true that an amplify push will create the ./aws-exports.js file,
but it will also "push" it to the server, overwriting whatever is there.
amplify status is also a handy command, similar to git status
I ran amplify env pull
and then found it in the ./src/aws-exports.js
not sure if the pull did it, or if it was always there but this is for an existing expo project
Confing your projects, using terminal go to the main folder and amplify init to config your project
amplify init
Do you to use an existing environment? (Y/n) Y
Choose the environment you would like to use: dev
Choose your default editor: Visual Studio Code
Choose the type of app you're building: javascript
What javascript framework you're using: ionic
Source Directory Path: src
Distribution Directory Path: www
Build Command: npm run-script build
Do you want to use an AWS profile? Y
Please choose the profile you want to use: select your personal IAM profile
Working on a web app using react.js that I picked up from another developer. Currently, trying to use AWS Amplify and I will eventually use AWS Cognito for authentication purposes.
I am using the following tutorial: https://hackernoon.com/react-authentication-in-depth-4deebda9aa45
I've already executed the following commands:
$ npm i -g #aws-amplify/cli
$ amplify configure
I've set up my CLI with the amplify config command, to include setting up the environment, access key ID and Secret Access key.
Error comes after running
$ amplify init
I've already seen a stack overflow post that states that this is a known error for the CLI, and that a fix has been implemented in the latest version of the CLI. I've tried updating amplify and re-installing. This is my second attempt to reinstall.
Here is a copy of the error in terminal.
MacBook-Air% amplify init
Note: It is recommended to run this command from the root of your app directory
? Do you want to use an existing environment? Yes
? Choose the environment you would like to use: discrete
Using default provider awscloudformation
✖ There was an error initializing your environment.
init failed
{ AccessDenied: Access Denied
at Request.extractError (/usr/local/lib/node_modules/#aws-amplify/cli/node_modules/aws-sdk/lib/services/s3.js:585:35)
at Request.callListeners (/usr/local/lib/node_modules/#aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/usr/local/lib/node_modules/#aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/usr/local/lib/node_modules/#aws-amplify/cli/node_modules/aws-sdk/lib/request.js:683:14)
at Request.transition (/usr/local/lib/node_modules/#aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/usr/local/lib/node_modules/#aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /usr/local/lib/node_modules/#aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request.<anonymous> (/usr/local/lib/node_modules/#aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
at Request.<anonymous> (/usr/local/lib/node_modules/#aws-amplify/cli/node_modules/aws-sdk/lib/request.js:685:12)
at Request.callListeners (/usr/local/lib/node_modules/#aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
message: 'Access Denied',
code: 'AccessDenied',
region: null,
time: 2019-05-01T18:09:17.901Z,
requestId: '7814262360A7DF07',
extendedRequestId:
'Y1woT4qs3VOtSCQG7sWNu7zexB2O+ZNP3oiBugTdfkHbK4Um5vzOS05P5qsZRcRFUPVTAbey8Q0=',
cfId: undefined,
statusCode: 403,
retryable: false,
retryDelay: 155.200421877319 }
Expect environment to properly initialize and amplify to be properly configured.
In my case, I cloned a repo from codecommit and doing amplify init and facing the same problem. To solve this, I rename aws-export.js to aws-export.mjs and again run amplify init and it initialize the project without any error.
You can check those issues reported at github project.
We had a similar issue using '#aws-amplify/cli' is version: '2.0.0', at aws Amplify Console.
Our envs develop, PR, etc. were building fine but master did not.
So, we change the version from 2.0.0 to 4.0.0 and build start working again.
Check
Console broken again (probably related to aws-amplify/cli 2.0.0)
AccessDenied error when deploying backend
It looks like the git repo has already teamproviderinfo.json present or some environment setting checking conflicting with your current setting. So when you try to init the project with environment name 'dev' or the one with the copied repo from git, it is trying to reuse the existing resources.
Solution: Try using a different name for the environment instead of dev and see if that works.
In my case it solved such issue.
We are building an application that so far has a simple user management implementation. This question relates to the built-in password resetting functionality of Loopback v3. User management is being worked on a model derived from the built-in User, and it is called MyCustomUser
Each time code changes are pushed into a GitHub repo, we have Jenkins build a Docker container, and inside of it run npm install then lb-sdk (with suitable parameters) then ng build --env=prod and finally node .. After this happens, the application runs normally, BUT:
When performing the same deployment commands locally (on my own linux laptop), the API endpoints /MyCustomUsers/reset and /MyCustomUsers/reset-password are created (i.e. they are visible and manipulable via the Strongloop Explorer)
When the deployment is run by Jenkins in the Docker container, only one of the two API endpoints is created, /MyCustomUsers/reset. God only knows where the other endpoint, /MyCustomUsers/reset-password, ends up.
Obviously, all deployments are run against the same codebase (i.e. the same commit ID of the GitHub repo). It is bewildering how the service behaves perfectly on localhost but not on the cloud-based docker container.
Sounds like you are running two different versions of the Loopback-Angular2-SDK. From what I've understood the SDK for Angular2 is still in heavy beta and not yet ready for production. However this doesn't excuse the difference, but it really sounds like two different versions.
We are using the same build-flow as you, are your package.json identical when it comes to #mean-expert/loopback-sdk-builder?
The guys working with the SDK-generator are really good at responding in their issue-section, would recommend asking there otherwise.
It turns out that the remote docker was running node 6.9.2 and npm 3.10.9, whereas I was running node 6.10.3 and npm 3.10.10. After making the docker instance run the same versions as I had locally and deploying the package.json along with its npm-shrinkwrap.json, the endpoint was correctly generated.