Beyond S3, Elastic Beanstalk also allows users to publish to it via Git, using a proprietary extension (not documented in the AWS Docs). By looking at some sources, basically, it seems AWS Exposes a Custom Endpoint for publishing
Using the canonical git, it works, but when using jgit, it throws an exception due to a wrong content type. Other than that, it actually works (as a new application version is thrown)
I attached some wire logs from Java into this URL:Â
Now the real questions:
a. Are those content-types mandatory?Â
b. Are there any circunventing options?