actions-marketplace-validations/Partslogic forked Beanstalk Deploy

Deploy a zip file to AWS Elastic Beanstalk

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stale
License: None
Runtime: Deprecated runtime

Inputs

name	description	required	default
aws_access_key	AWS Access Key	yes	—
aws_secret_key	AWS Secret Key	yes	—
aws_session_token	AWS Session Token when using temporary security credentials such as when assuming a role in AWS through STS	no	—
region	AWS Region	yes	—
application_name	Beanstalk application name	yes	—
environment_name	Beanstalk environment name. If empty a version will be created but not deployed anywhere.	no	—
version_label	Version label for new Beanstalk version	yes	—
version_description	Version description for the new Beanstalk version	no	—
deployment_package	Zip file with the version to deploy. If skipped the action will deploy existing version.	no	—
existing_bucket_name	Whether the action should skip creating a new bucket and use the given one to upload the deployment package to instead. When omitted the actions will (try to) create a new one during deployment.	no	—
use_existing_version_if_available	If set to "true" then the action will deploy an existing version with the given version_label if it already exists, but otherwise create the version and deploy it. If set to true for an action with no environment name it will upload a version if it does not exist already, but do nothing if the version already exists.	no	—
wait_for_deployment	Whether the action should wait for the deployment to finish and log status messages during the wait. Default is "true". If set to "false" the action will start the deployment on Beanstalk and then exit.	no	—
wait_for_environment_recovery	How many seconds to wait for the environment to return to Green state after deployment is finished. Default is 30 seconds.	no	—

Outputs

no outputs