Currently building a suite of tools on AWS serverless universe for hiring support of SMBs and startups. I self-identify as a Jedi and push to master branch.
This is a terrific workflow process and amplify has really come far. I have been working on backend stuff with SAM and need to revisit frontend.
At the step when the lambda function needs to be updated, I am not getting the same choices reflected in the writeup, i.e. "
Environment variables configuration" using SAM CLI 1.25.0. My menu says, "1. resource access permissions, scheduled recurring invocation, lambda layers configuration" with the obvious choice being the first one. But this decision path doesn't continue your workflow. Welcome any tips. Thanks.
Hey Vince! Glad you liked the post! Environment variables were just released last week. Have you had a chance to update your CLI to the latest version?
Currently building a suite of tools on AWS serverless universe for hiring support of SMBs and startups. I self-identify as a Jedi and push to master branch.
Things move fast in the AWS universe! I think I upgraded just the previous week. That was the issue. Thanks again for the fast response and series. Kudos.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a terrific workflow process and amplify has really come far. I have been working on backend stuff with SAM and need to revisit frontend.
At the step when the lambda function needs to be updated, I am not getting the same choices reflected in the writeup, i.e. "
Environment variables configuration" using SAM CLI 1.25.0. My menu says, "1. resource access permissions, scheduled recurring invocation, lambda layers configuration" with the obvious choice being the first one. But this decision path doesn't continue your workflow. Welcome any tips. Thanks.
Hey Vince! Glad you liked the post! Environment variables were just released last week. Have you had a chance to update your CLI to the latest version?
npm i -g @aws-amplify/clinpm i -g @aws-amplify/cli
Things move fast in the AWS universe! I think I upgraded just the previous week. That was the issue. Thanks again for the fast response and series. Kudos.