amplify-backend
amplify-backend copied to clipboard
aws-amplify
Home to all tools related to Amplify's code-first DX (Gen 2) for building fullstack apps on AWS
From https://github.com/aws-amplify/amplify-js-samples-staging/pull/765#discussion_r1436674841 . It appears that releasing a breaking change to `@aws-amplify/plugin-types` does not propagate correctly to `@aws-amplify/backend-cli` that also depends on this transitively. Note that breaking change in `@aws-amplify/plugin-types`...
From https://github.com/aws-amplify/amplify-backend/pull/895#pullrequestreview-1812156772 . And from related PRs https://github.com/aws-amplify/amplify-backend/pull/892 and https://github.com/aws-amplify/amplify-backend/pull/892 . We should revisit how strict do we want to be when asserting versions of packages defined in `amplify-backend` once...
### Environment information ```plain text N/A ``` ### Description As on today Amplify generated backend resources do not follow any standard naming convention to indicate important details like which amplify...
### Environment information ```plain text n/a ``` ### Description see title
### Environment information ```plain text System: OS: macOS 14.2.1 CPU: (10) arm64 Apple M1 Pro Memory: 890.36 MB / 32.00 GB Shell: 3.6.4 - /opt/homebrew/bin/fish Binaries: Node: 20.10.0 - ~/Library/Caches/fnm_multishells/77574_1680319338649/bin/node...
Today, when a lower level error happens in sandbox the entire stack trace is exposed to the customer. We should capture lower level errors and only expose them on DEBUG...
Calling SIGNIT on the Sandbox process while a deployment is in progress results in an uncaught exception. An option for the DX would be to warn the developer and confirm...
Related to: [829 comment](https://github.com/aws-amplify/amplify-backend/pull/829#pullrequestreview-1787880562) To keep track of @edwardfoyle concern related to exposing this API before releasing this feature
Related to [829 comment](https://github.com/aws-amplify/amplify-backend/pull/829/files#r1433068559) API GW endpoint should be exported from top level stack.
Related to: [#829 comment](https://github.com/aws-amplify/amplify-backend/pull/829/files#r1436534758) Amplify Auth construct creates user attribute in order to prevent issues when disabling passwordless that couldnt update user pool
Metadata
Owner
Metadata
Home to all tools related to Amplify's code-first DX (Gen 2) for building fullstack apps on AWS