Closed afosterw closed 6 years ago
Were you creating or updating your service?
Also, what version of boto3 do you have installed?
It happens on info, create and delete:
boto==2.46.1 boto3==1.5.18 botocore==1.8.39
I fixed locally with this change:
diff --git a/deployfish/aws/ecs.py b/deployfish/aws/ecs.py
index d472abe..724cf60 100644
--- a/deployfish/aws/ecs.py
+++ b/deployfish/aws/ecs.py
@@ -1273,7 +1273,7 @@ class Service(object):
for t in self.tasks.values():
t.from_aws(helpers[t.family])
- if self.__aws_service['serviceRegistries']:
+ if 'serviceRegistries' in self.__aws_service:
self.serviceDiscovery = ServiceDiscovery(self.service_discovery[0]['registryArn'])
else:
self.serviceDiscovery = None
Ah, those are old versions of boto3 and botocore. Could you update to latest and try again?
Current is:
boto3==1.7.49 botocore==1.10.49
You need to keep botocore and boto3 up to date so they can match changes to the upstream AWS API.
Yes, looking through the changelogs for botocore, the 'serviceRegistries' keyword was added in botocore==1.9.15, so the minimum requirement for boto3 looks like it would be 1.6.15.
I'll update the requirements appropriately.
I've released the requirements change to PyPi as deployfish==0.21.1 .
Thanks! I've updated to the latest boto/botocore and it's resolved on my end.
On Tue, Jul 3, 2018 at 3:54 PM, Chris Malek notifications@github.com wrote:
I've released the requirements change to PyPi as deployfish==0.21.1 .
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/caltechads/deployfish/issues/23#issuecomment-402274250, or mute the thread https://github.com/notifications/unsubscribe-auth/AAmMWo9y4J-i0OF_xOFGQGzt-xMtzTT0ks5uC8vpgaJpZM4VBf7w .
With config: