Where communities thrive

Join over 1.5M+ people
Join over 100K+ communities
Free without limits
Create your own community

Explore more communities

AWS Amplify/Lobby

People

Repo info

Activity

benjamin79

@benjamin79

type User @model @key(fields: ["customerId"]) { id: ID! firstname: String lastname: String! email: AWSEmail customer: Customer @connection(fields: ["customerId"], name: "CustomerUsers") }

export const syncUser = query SyncUser( $filter: ModelPersontempFilterInput $limit: Int $nextToken: String $lastSync: AWSTimestamp ) { syncPersontemps( filter: $filter limit: $limit nextToken: $nextToken lastSync: $lastSync ) { items { id...

The first one os the model i have. The second one the generated query from amplify codegen. Anything wrong here? Where would i set a customerId which to query?

nagendran

@Im_Nagu_twitter

Hi , Is there way to redirect the user to the original url he typed after authentication using amplify ? like I used localhost:7000/nagendran after login I get redirected to localhost:7000.. I need to be redirected to localhost:7000/nagendran

Daniel S. Dantas

@dantasfiles

@benjamin79 there's some weirdness in datastore right now, it could be affecting you aws-amplify/amplify-cli#3108

benjamin79

@benjamin79

@dantasfiles So the code above looks correct so far to you?

But where would the customerId be set in the client?

The datastore docu says is only queries the local database. But there is no documentation on how to alter the generated queries from codegen

eliasericsson

@eliasericsson

Hi all, I've run into an issue with Cognito and I think the best action here is to delete the user pool and start over. Is there any drawbacks to deleting the cognito stack in CloudFormation and do amplify push?

Daniel S. Dantas

@dantasfiles

@benjamin79 sorry, I don't know enough about datastore, I just saw that issue in github a while back and figured I'd let you know, someone else may be able to help

@eliasericsson any reason you don't just do amplify remove auth?

eliasericsson

@eliasericsson

I wan't to keep the setup I have locally but push it again

eliasericsson

@eliasericsson

@dantasfiles I forgot to tag you, do you know any good way to achieve this?

Daniel S. Dantas

@dantasfiles

@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

eliasericsson

@eliasericsson

@dantasfiles Then that's what I'll do, pray for me :)

Daniel S. Dantas

@dantasfiles

@eliasericsson I salute you, gladiator

eliasericsson

@eliasericsson

@dantasfiles ...yeah, that was propbably not a great idea to go through with. But now I instead ran amplify init and created a new env. Might work!

shrirupa

@shrirupa

Hi everyone, is there a way to get notified of amplify build status on slack.

Erich L Timkar

@erich-team

@eliasericsson In those case I switch to or create a different env, delete the original env and the recreate it.

eliasericsson

@eliasericsson

@erich-team Yeah, that's what I ended up doing. Annoyingly some of the modifications I had done to the CloudFormation templates didn't persist (by design maybe) and had to be recreated.

Erich L Timkar

@erich-team

So, I want to set the destination of the output of a funciton. Obviously, I can do this through the interface. Anyone have any guidance on doing this with amplify?

eliasericsson

@eliasericsson

@erich-team Output of a lambda?

Erich L Timkar

@erich-team

It’s been my assumtpion that what I pass to the callback, on success, gets passed to the destination funciton as part of the event.

Daniel S. Dantas

@dantasfiles

@erich-team how are you calling the lambda from your client: api gateway? graphql @function directive? something else?

Erich L Timkar

@erich-team

@dantasfiles s3 trigger actually.

Amplify provided that setup qite nicely. I suppose, I’m looking for the most amplify friendly solution to use multiple lamba funcitons in concert

Daniel S. Dantas

@dantasfiles

@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

Mike Swartz

@mswartz

hi gang, I'm having a really hard time getting the cli to work, running into an error that says

init failed TypeError [ERR_INVALID_ARG_TYPE]: The 'request' argument must be string. Received type undefined

when I try to use amplify-init

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.

Srinivas Gangji

@srinivas-gangji

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 ?

Clay Mitchell

@claym

can you connect a branch to more than one front end?

Jeff Finley

@quickliketurtle

@mswartz It’s possible it’s a dependancy issue or version conflict issue. I’ve seen success in deleting package-lock.json and node_modules and re-running npm install. Make sure to have a clean repo so you can roll back if needed.

Jeff Finley

@quickliketurtle

@claym Not sure I understand the question. Do you mean you have 2 front end apps and you want them to use the same amplify environment? Or that you have 2 front ends in the same git repo and want to deploy them at the same time? Or something else?

Clay Mitchell

@claym

@quickliketurtle i'm not sure, i'm trying to figure out what @srinivas-gangji is doing :D

Jeff Finley

@quickliketurtle

@claym Ah, i missed that. :-)

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…

Clay Mitchell

@claym

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

Jeff Finley

@quickliketurtle

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…

Clay Mitchell

@claym

@quickliketurtle yeah, not sure i like that either.

Jeff Finley

@quickliketurtle

What about checking for a user manually with things like Auth.currentAuthenticatedUser() to decide what happens different in you app. Then having a login button render <Authenticator>?

Christian Hufgard

@chufgard

Hi! Did anybody manage to use svelte within amplify?

julianljk

@julianljk

Hello, wanted to ask, is it possible to require phone number on sign up AND allow sign up with facebook at the same time? Following the manual auth setup in the auth cli, it doesn't seem to let me do that

Robert

@RobertBroersma

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?

plasrulz

@plasrulz

@senorpatricio I've figured out how to make a call finally

Srinivas Gangji

@srinivas-gangji

@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.

Erich L Timkar

@erich-team

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.

Erich L Timkar

@erich-team

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

Patrick Harding

@senorpatricio

@plasrulz nice.

plasrulz

@plasrulz

@senorpatricio yeah it was a great learning curve,

now I'm busy leanring the aws data modeling, security and storage opeartion and all is runnign pretty well.

Chat via Matrix