amplify-backend
amplify-backend copied to clipboard
Home to all tools related to Amplify's code-first DX (Gen 2) for building fullstack apps on AWS
### Is this related to a new or existing framework? _No response_ ### Is this related to a new or existing API? _No response_ ### Is this related to another...
Because we only look at the files that exist AFTER the change is made, and not those which were previously defined before the rename, we incorrectly call these renames large...
### Environment information ```plain text System: OS: macOS 13.6.3 CPU: (8) arm64 Apple M1 Memory: 120.47 MB / 16.00 GB Shell: 3.6.1 - /opt/homebrew/bin/fish Binaries: Node: 18.18.0 - ~/.local/share/nvm/v18.18.0/bin/node Yarn:...
When adding a social provider, the cdk stack outputs display the client ID which may not be ideal for customers who would like to keep the credentials a secret
### Environment information ```plain text System: OS: Windows 11 10.0.22000 CPU: (8) x64 Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz Memory: 3.06 GB / 15.92 GB Binaries: Node: 18.0.0 - ~\scoop\apps\nodejs\current\node.EXE...
### Description Investigate why the `never` assertion is necessary here: https://github.com/aws-amplify/amplify-backend/pull/759/files/ad080c5794d15eaf7e872b6a306ba3a590eeba1b#diff-11f0953eecd637d6180d8bf7763c67324f704242b7401015b3866fc2e5f48ff4 This error does not happen when building the same schema in a standalone project.
### Description Investigate why [this syntax error](https://github.com/aws-amplify/amplify-backend/pull/742#discussion_r1408580070) was not caught in e2e runs
### Environment information ```plain text System: OS: macOS 13.5 CPU: (10) arm64 Apple M1 Pro Memory: 574.00 MB / 32.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 18.18.2 - /usr/local/bin/node...
### Environment information ```plain text N/A ``` ### Description Aggregating large amount of data in memory is not ideal. See if we can stream it to the clients who need...
When I run `npx amplify sandbox` the second line that is printed says "executing command 'deploy'", which sounds like it's running `npx amplify deploy` with some sandbox-specific parameters. However, this...