Marcus Malcom comments

Results 29 comments of


                                            Marcus Malcom

Groups authorization not working as expected for GraphQL transformer v2 - Not Authorized

@chrisbonifacio - right, this is not how things are supposed to work, so we are agreed. This is a bug.

amplify push results in The runtime parameter of nodejs12.x is no longer supported for creating or updating AWS Lambda functions

Not sure if this matters or not but I'm using: GraphQL transformer version: 1

amplify push results in The runtime parameter of nodejs12.x is no longer supported for creating or updating AWS Lambda functions

@ykethan - just to be sure ... these Lambda functions are being created by aws amplify cli ... my project doesn't have any custom Lambda functions. The `PinpointFunction` and `UserPoolClientLambda`...

amplify push results in The runtime parameter of nodejs12.x is no longer supported for creating or updating AWS Lambda functions

@ykethan - ....... So let me get this straight ... I have had a project going for many years and then yesterday I do a push. This results in the...

amplify push results in The runtime parameter of nodejs12.x is no longer supported for creating or updating AWS Lambda functions

@ykethan - ok so I am trying to follow the steps https://github.com/aws-amplify/amplify-cli/issues/13788#issuecomment-2126049333 and https://github.com/aws-amplify/amplify-cli/issues/13788#issuecomment-2127303131 providing this information. I installed installed Amplify CLI @ 11.1.0: ``` npm install -g @aws-amplify/[email protected] ```...

amplify push results in The runtime parameter of nodejs12.x is no longer supported for creating or updating AWS Lambda functions

@ykethan - any chance we could get a new version of Amplify CLI that creates the `PinpointFunction` Lambda with the correct vesion?

amplify push results in The runtime parameter of nodejs12.x is no longer supported for creating or updating AWS Lambda functions

@ykethan - any updates on this? Development is blocked 100% because of this issue.

Add env name to the "aws-exports.js"

Any updates on this? This seems pretty simple to implement and would be very useful. The workaround above does not work for me (I have graphql and my URL doesn't...

GraphQL Transformer v1 to v2 migration - @searchable with auth rule for groupsField is not returning results from OpenSearch

@chrisbonifacio - thanks for the response. Please see log output from AppSync: [ad81162c-5fda-48c5-af70-69ba2bbc0f74_log.txt](https://github.com/user-attachments/files/18011955/ad81162c-5fda-48c5-af70-69ba2bbc0f74_log.txt). Response is empty array: ``` { "data": { "searchResearchSubjects": { "items": [] } } } ``` Also...

GraphQL Transformer v1 to v2 migration - @searchable with auth rule for groupsField is not returning results from OpenSearch

@chrisbonifacio yes the project is using Cognito auth. Here are all the resolvers for that query: [Query.searchResearchSubjects.auth.1.req.vtl.txt](https://github.com/user-attachments/files/18014938/Query.searchResearchSubjects.auth.1.req.vtl.txt) [Query.searchResearchSubjects.postAuth.1.res.vtl.txt](https://github.com/user-attachments/files/18014939/Query.searchResearchSubjects.postAuth.1.res.vtl.txt) [Query.searchResearchSubjects.req.vtl.txt](https://github.com/user-attachments/files/18014940/Query.searchResearchSubjects.req.vtl.txt) [Query.searchResearchSubjects.res.vtl.txt](https://github.com/user-attachments/files/18014941/Query.searchResearchSubjects.res.vtl.txt) Thank you