Deployment failed: Error: Status: 400. Code: InvalidParameterValue, Message: No Application Version named '886765199' found.
See original GitHub issueIssue Description
Everything I try results in an error, it seems impossible to use. This is my config:
steps:
- name: checkout
uses: actions/checkout@v2
- name: Generate deployment package
run: zip -r deploy.zip docker-compose.yml Dockerrun.aws.json
- name: Deploy to Elastic Beanstalk
uses: einaregilsson/beanstalk-deploy@v17
with:
aws_access_key: ${{ secrets.AWS_ACCESS_KEY_ID }}
aws_secret_key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
application_name: archimedes
environment_name: dev-archimedes
region: eu-west-1
version_label: ${{github.run_id}}
version_description: none
deployment_package: deploy.zip
ERROR: Deployment failed: Error: Status: 400. Code: InvalidParameterValue, Message: No Application Version named ‘886765199’ found.
Using existing version
steps:
- name: checkout
uses: actions/checkout@v2
- name: Generate deployment package
run: zip -r deploy.zip docker-compose.yml Dockerrun.aws.json
- name: Deploy to Elastic Beanstalk
uses: einaregilsson/beanstalk-deploy@v17
with:
aws_access_key: ${{ secrets.AWS_ACCESS_KEY_ID }}
aws_secret_key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
application_name: archimedes
environment_name: dev-archimedes
region: eu-west-1
version_label: Sample Application
version_description: none
deployment_package: deploy.zip
ERROR: Deployment failed: Version Sample Application already exists. Either remove the “deployment_package” parameter to deploy existing version, or set the “use_existing_version_if_available” parameter to “true” to use existing version if it exists and deployment package if it doesn’t.
With use_existing_version_if_available: true
steps:
- name: checkout
uses: actions/checkout@v2
- name: Generate deployment package
run: zip -r deploy.zip docker-compose.yml Dockerrun.aws.json
- name: Deploy to Elastic Beanstalk
uses: einaregilsson/beanstalk-deploy@v17
with:
aws_access_key: ${{ secrets.AWS_ACCESS_KEY_ID }}
aws_secret_key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
application_name: archimedes
environment_name: dev-archimedes
region: eu-west-1
version_label: "Sample Application"
version_description: none
deployment_package: deploy.zip
use_existing_version_if_available: true
ERROR: Error: Deployment failed: TypeError: Cannot read property ‘VersionLabel’ of undefined
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:16 (7 by maintainers)
Top Results From Across the Web
AWS BeanstalkL ERROR: InvalidParameterValueError - No ...
Okay I managed to get the deployent to work and it matches up under versions in the beanstalk dashboard. I went into the...
Read more >beanstalk-deploy - Bountysource
Deployment failed : Error: Status: 400. Code: InvalidParameterValue, Message: No Application Version named '886765199' found. $ 0.
Read more >Notifications and troubleshooting - AWS Elastic Beanstalk
A 400 series status code indicates that the user made a bad request, such as requesting a page that doesn't exist (404 File...
Read more >[SOLVED] No Application Version named 'myapp-1' found.
Hello, I am having issues with deploying my app to AWS Elastic Beanstalk. I receive a very weird error because I have an...
Read more >create-application-version — AWS CLI 2.9.7 Command ...
If no application is found with this name, and AutoCreateApplication is false , returns an InvalidParameterValue error. --version-label (string). A label ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was using the wrong AWS region…if anyone else ever has this issue…
@jclaessens97 Ok, thanks for reporting back! And yes, very weird that it doesn’t just throw an error but gives you an empty response, that’s just guaranteed to get users to spend lots of time trying to figure out what’s wrong!