instance-scheduler-on-aws
instance-scheduler-on-aws copied to clipboard
Build improvements
Description of changes: This allows custom deployments of the project by:
- allowing different acls for artifacts on S3
- not requiring a mirror bucket in the region, which is obviously something only AWS solutions has.
I don't think this should break anything in your current workflow, apart for requiring jinja to have proper templating. Pipenv config was added, so that should be a plus as well.
I can deploy with:
$ make bucket=xyz-instancescheduler acl=private acl_remote=public-read s3_mirrors=false deploy
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.