Edward Foyle

Hi all, so far I'm unable to repro this using v 9.2.1 of the CLI. Is anyone still having this issue on that version?

HI @benjeater for some reason it seems like you `team-provider-info.json` file is not being updated correctly when creating / checking out a new environment or not being persisted to your...

Hi @JackWSargent we can look into increasing the environment variable length limitation. However, based on what you've described, it seems like [function secrets](https://docs.amplify.aws/cli/function/secrets/#configuring-secret-values) may be more appropriate for your use...

@SaileshKumar if the auth resource in your sandbox / internal environments doesn't contain any user data that you need to retain, the simplest solution would be to delete and recreate...

Hi @tan-t thanks for the contribution. It looks like the tests are failing. Can you take a look at the errors and make sure that the tests are passing.

@michaelbrewer You're right that pipenv is overkill for small functions that only have a couple dependencies, but it is good for managing functions with lots of dependencies. It is also...

This PR needs some E2E updates that I haven't gotten around to yet

Hi @jakemitchellxyz thanks for writing up this detailed report and sorry for the inconvenience it's caused. The team will evaluate adding the feature flag you suggested and will also consider...

Hi @gspeicher I think this may be a duplicate of https://github.com/aws-amplify/amplify-cli/issues/10141 Can you confirm that you have the [`generateGraphQLPermissions`](https://docs.amplify.aws/cli/reference/feature-flags/#generateGraphQLPermissions) feature flag enabled? After enabling that feature flag, running `amplify update...

Hi @OperationalFallacy, unfortunately there isn't currently a mechanism for parameterizing those values between environments. What you are currently doing is probably the best workaround (although I agree it's clunky). Marking...