summaryrefslogtreecommitdiff
path: root/ChangeLog
diff options
context:
space:
mode:
authorScott Moser <smoser@ubuntu.com>2012-11-13 14:13:12 -0500
committerScott Moser <smoser@ubuntu.com>2012-11-13 14:13:12 -0500
commitb503a6827a8aca13246e98272d83cf11fdeab820 (patch)
tree98623afdac904191c8fddc284fd48ba85739949a /ChangeLog
parent7ea93af0599fc10d69c059e86e3f6e027b8ba7b4 (diff)
parent10147364638595d6c1a7077cc47c205413ef13a6 (diff)
downloadvyos-cloud-init-b503a6827a8aca13246e98272d83cf11fdeab820.tar.gz
vyos-cloud-init-b503a6827a8aca13246e98272d83cf11fdeab820.zip
Even when using boto < 2.6 force the unlazying to occur
It seems like its possible that boto 2.5.2 and below have the lazy loading metadata dictionary so as a precaution we will always take the hit of unlazying the metadata dictionary by traversing it which in the non-lazy dictionary case has no effect (its marginal). This also removes the need to check the boto version and the dependency on setup tools just for this case.
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog3
1 files changed, 1 insertions, 2 deletions
diff --git a/ChangeLog b/ChangeLog
index 14efc4b1..3735b1e1 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -38,9 +38,8 @@
runs the usage of this lazy loading is hidden and since that lazy loading
will be performed on future attribute access we must traverse the lazy loaded
dictionary and force it to full expand so that if cloud-init blocks the ec2
- metadata port the lazy loaded dictionary will continue working properly
+ metadata port the lazy loaded dictionary will continue working properly
instead of trying to make additional url calls which will fail (LP: #1068801)
- - Added dependency: python-pkg-resources (deb), python-setuptools (rpm)
- use a set of helper/parsing classes to perform system configuration
for easier test. (/etc/sysconfig, /etc/hostname, resolv.conf, /etc/hosts)
0.7.0: