amplify-cli: Why OpenSearchStreamingLambdaFunction does not have app name prefix and current env suffix?
Which Category is your question related to? API
Amplify CLI Version 7.6.7
What AWS Services are you utilizing? Amplify
Provide additional details e.g. code snippets
Pushing minor updates in schema caused changing search lambda name to OpenSearchStreamingLambdaFunction - without app name or environment. Is this expected behaviour?
Trying to push to production now causes error:
OpenSearchStreamingLambdaFunction already exists in stack
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 5
- Comments: 20 (4 by maintainers)
If possible, can someone from Amplify team recommend a workaround, e.g. do we downgrade the CLI version?
Customers unable to deploy to production environments should be treated as a high-severity issue
Please deploy the fix ASAP, downgrading to 7.6.5 introduces other issues and is not an acceptable workaround
I’ve got the same issue.
As of 7.6.7, it changes the previous OpenSearchStreamingLambda function from
amplify-<appName>-<env>-OpenSearchStreamingLambd-<someId>toOpenSearchStreamingLambdaFunction, without any other identifier.I updated my dev env, but I can no longer push to prod, due to the error: Following resources failed Resource Name: amplify-<appName>-<env>-OpenSearchStreamingLambd-<someId> (AWS::Lambda::Function) Event Type: update Reason: OpenSearchStreamingLambdaFunction already exists in stack <LambdaArn>
@Rafcin I don’t think the fix has been released yet, 7.6.9 was released 21 hours ago, but the fix was only merged 9 hours ago
Edit I’m stupid, ignore this. Thank you.
I don’t wanna be that guy, but 7.6.9 gave me some funky IAM/OS errors 😦