amplify remove auth?
#current-cloud-backenddirectory, you could theoretically delete your cloudformation stack on AWS and then alter
#current-cloud-backendto make amplify think it hasn't pushed your auth, but I am nowhere near brave enough to try that
4.2.0of the cli, but I have that version and it's still doing this. not finding much else in the way of help on this.
npm cidoesn't install the dependencies, as a result, the required dependencies are missing , which causes the build failure. Is anyone else having similar issue ?
withAuthenticationbut 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?
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_APINAME
Amplify Params - DO NOT EDIT */// eslint-disable-next-line