Open josefaidt opened 2 years ago
Need more clarity on the problem :
The feature functionality works fine. Tested the following flows:
UX issues :
Moved issue to feature request to address UX upgrades
Do note that this is the error yielded when such layer doesn't exist on that region. I.e:
An error occurred (AccessDeniedException) when calling the UpdateFunctionConfiguration operation: User: arn:aws:iam::***:user/{username} is not authorized to perform: lambda:GetLayerVersion on resource: arn:aws:lambda:us-east-1:015030872274:layer:AWS-Parameters-and-Secrets-Lambda-Extension:4 because no resource-based policy allows the lambda:GetLayerVersion action
Pay special attention to the fact that account_ids may differ for the same aws managed lambda layer from region to region.
Before opening, please confirm:
How did you install the Amplify CLI?
pnpm add -g @aws-amplify/cli
If applicable, what version of Node.js are you using?
v16.13.0
Amplify CLI Version
7.3.3
What operating system are you using?
Mac
Amplify Categories
function
Amplify Commands
update
Describe the bug
After upgrading the CLI to the latest version (7.3.3), I am unable to update lambda layer permissions from a layer created with a previous version of the CLI (6.3.1)
A few observation notes:
Expected behavior
CLI should update the layer accordingly
Reproduction steps
using Amplify CLI v6.3.1, create a lambda layer:
amplify push -y
pnpm add -g @aws-amplify/cli@latest
Observe CLI exits with no clear indication of failed or successful update, running
amplify status -v
shows no changesGraphQL schema(s)
Log output
Additional information
No response