You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi - I'm sure I'm doing something wrong, but not quite sure what. I've been writing/testing lambdas locally successfully, and I'm now attempting to push to my staging env.
The CI flow is a github action (PHP based) that runs the vapor deploy staging command, then the deploy/activate divided between build & deploy stages as suggested in the docs.
The error I get at the 'activate' stage is:
Error executing "ListVersionsByFunction" on "https://lambda.***.
amazonaws.com/2015-03-31/functions/SC-Variant-Staging-staging-Sidecar-Sharp
ResizeImageLambda/versions?MaxItems=100"; AWS HTTP error: Client error: `GE
T https://lambda.***.amazonaws.com/2015-03-31/functions/SC-Varia
nt-Staging-staging-Sidecar-SharpResizeImageLambda/versions?MaxItems=100` re
sulted in a `404 Not Found
Looking at the lambdas deployed, I can see why the 404 occurs, as the only deployed staging version is 'SC-Variant-staging-Sidecar-SharpResizeImageLambda' (note the single, lowercase 'staging').
The text was updated successfully, but these errors were encountered:
benferns
changed the title
Environment name repeated twice in lambda activate
Error executing "ListVersionsByFunction": Environment name repeated twice in lambda name
Jun 18, 2021
Hmm... Is your APP_NAME different in staging? perhaps Variant Staging? I ask because I don't think I capitalize the env ever, so it may be coming from somewhere else.
That was it! I was wracking my brains trying to think all the places the name could come from, but was focusing on the vapor build process. Thanks for the help & the package itself!
On Fri, Jun 18, 2021 at 9:17 PM Ben Ferns ***@***.***> wrote:
That was it! I was wracking my brains trying to think all the places the
name could come from, but was focusing on the vapor build process. Thanks
for the help & the package itself!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGXKC6RYGPFKTBB4J4CYNLTTP443ANCNFSM465HPEMQ>
.
Hi - I'm sure I'm doing something wrong, but not quite sure what. I've been writing/testing lambdas locally successfully, and I'm now attempting to push to my staging env.
The CI flow is a github action (PHP based) that runs the vapor deploy staging command, then the deploy/activate divided between build & deploy stages as suggested in the docs.
The error I get at the 'activate' stage is:
Looking at the lambdas deployed, I can see why the 404 occurs, as the only deployed staging version is 'SC-Variant-staging-Sidecar-SharpResizeImageLambda' (note the single, lowercase 'staging').
The text was updated successfully, but these errors were encountered: