Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error executing "ListVersionsByFunction": Environment name repeated twice in lambda name #19

Closed
benferns opened this issue Jun 18, 2021 · 3 comments

Comments

@benferns
Copy link

benferns commented Jun 18, 2021

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').

@benferns benferns changed the title Environment name repeated twice in lambda activate Error executing "ListVersionsByFunction": Environment name repeated twice in lambda name Jun 18, 2021
@aarondfrancis
Copy link
Contributor

aarondfrancis commented 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.

Lemme know!

@benferns
Copy link
Author

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!

@aarondfrancis
Copy link
Contributor

aarondfrancis commented Jun 19, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants