Clever Geek Handbook

EB CLI parameterizes the deployment artifact name for CI deployments

Using EB CLI to deploy a pre-built application package. The related section config.yml looks like this:

deploy:
  artifact: Website.zip

However, the CI assembly creates a file with the added version:

Website-1.5.44.zip

Is it possible to specify a deployment artifact using a command like:

eb deploy --artifact "Website-1.5.44.zip"
#or
eb deploy --artifact "/path/to/Website-1.5.44.zip"

Are there any alternatives the EB CLI provides for deploying assembly versioned artifacts in CI pipelines? Perhaps I could rename the versioned zip file to Website.zip only and then run an eb deployment, but it would be nice to have the version in the artifact file name as well.

+3


source to share


2 answers


There is currently no way to do what you describe; there are no flags to instruct the EB CLI to use the custom artifact. While you have to call the artifact what is in yourconfig.yml



The added comment will save the artifact Website.zip

and name the application version Website-1.5.44.zip

. It will not use the artifact namedWebsite-1.5.44.zip

+1


source


The label flag will rename the file uploaded to AWS:



eb deploy --label Website-1.5.44.zip
0


source






More articles:


All Articles