You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
bellow the error message :
An error occurred (InvalidParameterValue) when calling the UpdateEnvironment operation: No Environment found for EnvironmentName = 'prod_env'.
knowing that prod_env is my application's environment in aws elastic beanstalk.
@Adelphe_MBATCHI hello, thanks for reporting.
Can you please share details of logs if possible and the part of the pipeline where it has failed?
There may be different reasons of failure like such some tiny mistakes in syntax, usage or sth else
image: node:10.20.1
pipelines:
default:
- step:
name: "Build and Test"
caches:
- node
script:
- npm install
- apt-get update && apt-get install -y
- apt-get install zip
- zip application.zip index.js package.json
services:
- mongo
artifacts:
- application.zip
- step:
name: "Deploy to Production"
deployment: 'Production'
script:
- pipe: atlassian/aws-elasticbeanstalk-deploy:0.6.4
variables:
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY
AWS_DEFAULT_REGION: 'us-east-1'
APPLICATION_NAME: 'cloudhse'
S3_BUCKET: 'elasticbeanstalk-us-east-1-307150017281'
ZIP_FILE: 'application.zip'
VERSION_LABEL: 'CloudHSE-${BITBUCKET_BUILD_NUMBER}'
ENVIRONMENT_NAME: 'prod_env'
definitions:
services:
mongo:
image: mongo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
build logs :
✔ Application version CloudHSE-31 successfully created in Elastic Beanstalk.
INFO: Updating environment in Elastic Beanstalk...
An error occurred (InvalidParameterValue) when calling the UpdateEnvironment operation: No Environment found for EnvironmentName = 'prod_env'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, @Adelphe_MBATCHI !
Could you try to execute aws cli command update-envronment to debug it?
Or just to check it if aws should recognize it:
aws elasticbeanstalk describe-environments --application-name "<app_name>" --environment-names "<env_name>" --debug
If it succeed then you can debug update command.
Looking forward hearing back from you.
Cheers, Galyna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.