josef
Hey @djsjr :wave: thanks for raising this! From your reproduction steps I noticed these environments are deleted and cloned from the Console rather than the CLI, however the CLI is...
Hey @ilkerburakkurt :wave: thanks for taking the time to file this! I've marked this as a bug to log a more helpful error message when attempting to export a stack...
Hey @HieronymusLex :wave: thanks for raising this! I was able to successfully reproduce this issue with the latest version of the CLI (7.6.19). Marking as a bug 🙂
Hey @AsitDixit :wave: you can use username as a login mechanism by selecting `username` when creating the auth resource with `amplify add auth` (https://docs.amplify.aws/cli/auth/overview/) Can you clarify the second question?...
Hey @AsitDixit apologies for the delay here, are you looking to have unique `preferred_username` attributes? This approach may create an additional attack vector for your app. We can also leverage...
Hey @AsitDixit just wanted to follow-up on this one and see if you're still experiencing this issue?
Hey @cfbo :wave: apologies for the delay, but thank you for taking the time to file this and include detailed reproduction steps! I was able to reproduce by creating a...
> If understood correctly, a workaround is the following: when merging branch 2 into branch 1 and while amplify is on envA, after resolving the git conflicts we should also...
note: potentially need to handle trailing slashes in libraries as well
Hey @jonschoning :wave: thanks for raising this! I've marked this as a feature request for the team to evaluate further 🙂