question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow uploading application version without deployment to environment

See original GitHub issue

Tell us about your request

In our CI system, I would like to build and upload application versions. I don’t want to commit my .eb configuration, I just want to run a command like eb deploy --application MyApp --label "$GIT_SHA" --description "$GIT_COMMIT_MSG".

Currently, the file .elasticbeanstalk/config.yml has to exist, and there’s no way to say “just upload the build, don’t deploy it to an environment”.

Are you currently working around this issue?

Building and uploading app version with a standalone shell script using aws cli.

Additional context

I would be happy to work on this, but I think some architectural decisions have to be made:

  • Will this FR be accepted
  • How to implement commands which don’t require eb init

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:8 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
halcarletoncommented, May 11, 2020

Gotcha, well it seems reasonable to me to want to create an application version outside of a deploy/create action. Especially because this is functionality that is supported in the AWS EB console.

I will leave this open while we review adding this to our roadmap.

1reaction
orestiscommented, Jun 12, 2020

Just chipping in here, we have a similar requirement with a different use case:

  • We want to be able to easily deploy any “green” branch (e.g. branches that pass all CI tests)
  • But we don’t want to immediately deploy when tests pass, just do all the pre-compilation etc and upload the build artifact somewhere (this could be S3 or something similar)
  • Then when we are ready to go, we can point to a pre-built artifact and deploy, which means we don’t have to go through building everything again.

Being able to generate and upload an artefact that’s ready for deployment would allow this workflow.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Managing application versions - AWS Elastic Beanstalk
Elastic Beanstalk creates an application version whenever you upload source code. This usually occurs when you create an environment or upload and deploy...
Read more >
Elastic Beanstalk CLI upload version without deploying
I would suggest using the AWS CLI to push the local zip into S3 then to upload using the Create Application Version method...
Read more >
Things to keep in mind while deploying to Elastic Beanstalk
The code which is currently deployed in the EB environment. Staging(/var/app/staging). When any new code version is being deployed, this ...
Read more >
AWS ElasticBeanstalk NodeJS Application version cannot be ...
I have a NodeJS application running via ElasticBeanstalk, have deployed 59 ... The "Application versions" page of the environment shows errors on loading...
Read more >
Deploying to AWS Elastic Beanstalk with Octopus
An application version is a copy of the code that is deployed to an ... be implemented without maintaining environment-specific artifacts.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found