Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate from boto2 to boto3. #86

Merged
merged 1 commit into from Jul 22, 2018
Merged

Migrate from boto2 to boto3. #86

merged 1 commit into from Jul 22, 2018

Commits on Jul 22, 2018

  1. Migrate from boto2 to boto3. 

    Boto3 has been out for some time now and boto2 will likely be
deprecated in months / years to come. Since most AWS users are
now on boto3, migrating Garcon to Boto3.

This upgrade introduces couple breaking changes:
* `Workflow` now needs a `client` (`boto3.client('aws', region_name='us-east-1')`)
  to work. It enables workflows to run on specific AWS regions.
* `ActivityExecution` is now passed to the Runner instead of the
  `Activity`. Similar to boto2 activities, you can perform operations
  on the execution such as `complete`, `fail` and `heartbeat`.
    @xethorn
    xethorn committed Jul 22, 2018
    Copy the full SHA
    50dd52c View commit details
    Browse the repository at this point in the history