We were implicitly relying on mongo to return the list of members in their _id order, which is absurd and I have no idea how we didn't catch it previously. We could do a little list comprehension to pull out the member with the same _id, but it seemed easier to just sort both lists and retain the original intent.
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| ec2_acl | Loading commit data... | |
| ec2_ami_2_0_0_1.py | Loading commit data... | |
| ec2_group_local | Loading commit data... | |
| ec2_iam_role | Loading commit data... | |
| ec2_lookup | Loading commit data... | |
| ec2_rt | Loading commit data... | |
| ec2_subnet | Loading commit data... | |
| ec2_tag_local | Loading commit data... | |
| ec2_vpc_local | Loading commit data... | |
| git_2_0_1 | Loading commit data... | |
| hipchat_2_0_0_1.py | Loading commit data... | |
| mongodb_replica_set | Loading commit data... | |
| mongodb_rs_status | Loading commit data... | |
| rds_local | Loading commit data... | |
| util_map | Loading commit data... | |
| vpc_lookup | Loading commit data... |