Skip to content

Issues: aws-amplify/amplify-backend

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
47 Open 76 Closed
47 Open 76 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Address failures that break telemetry tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#2010 opened Sep 16, 2024 by rtpascual
Amplify errors description is not printed in create amplify flows bug Something isn't working tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#1991 opened Sep 11, 2024 by ShadowCat567
Expand e2e test coverage to include generating amplify_outputs doesn't break with new version amplify_outputs Issue related to generating amplify_outputs for deployed backends generate Issues tied to generate command tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling
#1918 opened Aug 26, 2024 by Amplifiyer
Deploying an EdgeFunction bound to a CloudFront distribution with a Storage bucket as origin (Pass props for root Stack) feature-request New feature or request needs-product-input Needs non-technical requirements or direction to proceed tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#1663 opened Jun 17, 2024 by renevatium
1
Explicit public surface definition documentation Improvements or additions to documentation feature-request New feature or request tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#1533 opened May 16, 2024 by sobolk
1
Define naming strategy for symbols we inject in functions. feature-request New feature or request function Issue pertaining to Amplify Function tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#1524 opened May 15, 2024 by sobolk
document e2e test process repo-infrastructure Engineering label for issues related to repo infrastructure tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling
#1351 opened Apr 19, 2024 by sobolk
Lint rule for \n repo-infrastructure Engineering label for issues related to repo infrastructure tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#1294 opened Apr 12, 2024 by edwardfoyle
Lint rule for AmplifyUserError and AmplifyFault repo-infrastructure Engineering label for issues related to repo infrastructure tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#1293 opened Apr 12, 2024 by edwardfoyle
1
[Tech Debt] refactor into type PackageManagerInitializer and have sub-types with a factory. tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#1252 opened Apr 4, 2024 by 0618
investigate why windows create_amplify e2e test takes so long repo-infrastructure Engineering label for issues related to repo infrastructure tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling
#1198 opened Mar 22, 2024 by edwardfoyle
consider test-splitting strategy for expensive e2e tests repo-infrastructure Engineering label for issues related to repo infrastructure tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling
#1190 opened Mar 22, 2024 by edwardfoyle
[CICD] Windows run_e2e_tests timed out waiting for role deletion flaky Engineering label for flaky tests tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling
#1163 opened Mar 18, 2024 by rtpascual
[CICD] possible race condition creating AppSync data sources in data construct flaky Engineering label for flaky tests tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling
#1156 opened Mar 14, 2024 by edwardfoyle
[CICD] e2e tests fail with "Error: Unable to deserialize cloned data due to invalid or unsupported version." flaky Engineering label for flaky tests repo-infrastructure Engineering label for issues related to repo infrastructure tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling
#1145 opened Mar 13, 2024 by edwardfoyle
4
display UNTESTED_NODE_VERSION on command run feature-request New feature or request tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#1110 opened Mar 6, 2024 by ykethan
add e2e test for Vite and Nextjs tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling
#1038 opened Feb 16, 2024 by 0618
env info with node 16 or 21 shows banner bug Something isn't working tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#1000 opened Feb 6, 2024 by ykethan
1
@ykethan
remove yargs from create-amplify tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#972 opened Feb 1, 2024 by 0618
1
make execa version consistent tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#962 opened Jan 31, 2024 by 0618
[PASSWORDLESS TODO]: implications of exposing public API tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#913 opened Jan 11, 2024 by elorzafe
[PASSWORDLESS TODO]: cfn output should be exported from top level stack tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#912 opened Jan 11, 2024 by elorzafe
[PASSWORDLESS TODO]: confirm custom attribute for passwordless sign up tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#911 opened Jan 11, 2024 by elorzafe
Revisit dependency check - how do we enforce versions of packages in amplify-backend repo repo-infrastructure Engineering label for issues related to repo infrastructure tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
#897 opened Jan 9, 2024 by sobolk
API tests further improvements. repo-infrastructure Engineering label for issues related to repo infrastructure tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling
#871 opened Jan 5, 2024 by sobolk
1
ProTip! Find all open issues with in progress development work with linked:pr.