deploy eb package from folder (instead of requiring a zip file as an input)

[augustoproiete]

My team follows a common deployment workflow where binaries are built once, deployed to a testing environment, and at a later time (after passing tests) the same binaries are then deployed to other environments - the only difference between environments are configuration settings stored in files that are included in the deployment package itself, and are updated at deployment time.

Our process is all automated in our CI/CD pipeline, and we use dotnet eb package to create the .zip file that (at a later time) is deployed to the different environments via dotnet eb deploy-environment --package.

Given configuration settings differ between environments, we are required to unzip the package created by dotnet eb package just before deployment, in order to perform variable replacement in config files, run XSD transforms, etc. to prepare the configuration settings to match the target environment.

At this point, we have a folder with all the files in the desired state to be deployed to the target environment.

Because dotnet eb deploy-environment --package requires a .zip file as an input, we end up creating a new .zip file with the contents of the folder and deploy the new .zip file.

It would be useful if dotnet eb deploy-environment --package could take a folder as an input, as an alternative to taking a .zip file.

[github-actions]

We have noticed this issue has not recieved attention in 1 year. We will close this issue for now. If you think this is in error, please feel free to comment and reopen the issue.

[normj]

I think having the tool check to see if the path pointed to by the --package switch is a directory and if so zip it up sounds like a reasonable feature request. Would you be interested in submitting a PR for the feature request?

[github-actions]

We have noticed this issue has not received attention in 1 year. We will close this issue for now. If you think this is in error, please feel free to comment and reopen the issue.