@eliasericsson any reason you don't just do
amplify remove auth?
@eliasericsson amplify keeps track of what it pushed to the cloud by comparing the (local)
backend and (cloud) #current-cloud-backend directory, you could theoretically delete your cloudformation stack on AWS and then alter #current-cloud-backend to make amplify think it hasn't pushed your auth, but I am nowhere near brave enough to try that
Amplify provided that setup qite nicely. I suppose, I’m looking for the most amplify friendly solution to use multiple lamba funcitons in concert
@erich-team AWS uses Step Functions in the example app, but you probably can get away with something simpler like link them with SQS, or just call one from the other, if you're not doing anything complex, I think the trick is to make sure one function is not waiting on the other and burning lambda compute time
searching for this yields some closed issues, and the devs saying this is fixed in
4.2.0 of the cli, but I have that version and it's still doing this. not finding much else in the way of help on this.
Hello, I am having trouble deploying my amplify application when more than one branch is connected, the first connected branch's build ( i.e Frontend Build) works as expected, but the branches connected after keep failing. When looking at the console output, I observe that
npm ci doesn't install the dependencies, as a result, the required dependencies are missing , which causes the build failure. Is anyone else having similar issue ?
I read that as they have their app set up to deploy in the amplify console and the first branch is building successfully, say staging, but then production is failing on the npm ci command…
ok, so I have an app that can be used while logged in or logged out. I'd like to use the stock Authenticator component to log in, change passwords, whatever. Anybody know a good way to implement this? withAuthenticator forces it to always show, wrapping a component in <Authenticator> just shows it underneath it, i'm not exactly sure what the best option is
I’m not sure with using the Amplify UI components… Without them you’d have public and private routes… I’ve seen an implementation with returning seperate app instances for public pages and admin pages, with that you could wrap the admin app instance with
withAuthentication but I’m not sure I like it…
Does anyone have some pointers on CI/CD with AppSync/Amplify? I want to only deploy the graphql backend, no frontend hosting. Preferably deploy branch previews as well in CI/CD. Is that possible?
I read about switching envs in Amplify, would it make sense locally to create a git hook on post-checkout for switching envs or will this bite me in the ass?
@claym I have three branches ( dev, test, prod) connected to three environments ( dev, test, prod). The same build settings work fine while deploying build to 'dev' environment but fail while deploying to 'test' or 'prod', as I mentioned, I observe that 'npm ci' doesn't install the required packages while doing the build for 'test' or 'prod'
@quickliketurtle that's correct , thank you. sorry, my question was not very clear.
Having granted acces to another API to a lambda function, what’s best practice for accessing that API? Obviously, I can make a HTTP request with node-fetch (for example), but that I wasn’t sure if there was a tool to directly invoke an API within a lambda function similar to what is available in, say, the amlify-react tools.
To be more specific, when Amplify adds this info to a function to make the API accessible, what is the expected means of invoking the API
/* Amplify Params - DO NOT EDIT
You can access the following resource attributes as environment variables from your Lambda function
var environment = process.env.ENV
var region = process.env.REGION
var apiLogsApiName = process.env.API_LOGS_APINAMEAmplify Params - DO NOT EDIT */// eslint-disable-next-line
now I'm busy leanring the aws data modeling, security and storage opeartion and all is runnign pretty well.
Hello, I wanted to share an important lesson I learned while troubleshooting my issue (Please see my issue above). If NODE_ENV is set to 'production',
npm ci command will only install production dependencies. In my case, I had set NODE_ENV to 'production' in amplify console ( for 'test' and 'prod' branches) and was using npm ci to install the dependencies, the build step was failing, as this step would require 'dev' dependencies.
