lyft

Title: Try all AWS accounts, and raise Exception afterwards

Description:
Sometimes a single AWS account's sync could fail. In such situations, we more likely want to proceed with the rest of our accounts, but still be notified of the failure.

I propose to wrap _sync_one_account into a try-catch, invoke logger.exception for the failures, and then finally raise another exception lis

Description
When /tmp and the destination directory is mounted on a different disk then fails with following error

Expected Behavior
Should not fail
Actual Behavior

*** Your new workflow can be found here: /home/uva/opensource/clutch/frontend/workflows/amiibo
For information on how to register this new workflow see our configuration guide: https://clutch.sh/docs/configur

The error handling in the IPAM add command is such that it is very hard to understand why something is failing. I've run into two problems that are due to the same general issue:

1. The allocateClient doesn't differentiate between an interface already being maxed out on allowed IPv4 or IPv6 IP addresses and all IP addresses in a subnet being taken. Only the later is represented in the error [