boto / boto3

98%

develop: 91%

LAST BUILD ON BRANCH collisions

branch: collisions

CHANGE BRANCH

x

Reset

• collisions
• develop
• load-fix
• unique-meta
• collections
• repr
• install-fix
• model
• references
• loader
• equality
• region-config
• docs
• docs-fix
• error-info
• config-docs
• docs-refs
• reverse-jmespath
• master
• 0.0.1
• useragent
• deps
• integ
• doc-example
• 0.0.2
• model-update
• 0.0.3
• batch-actions
• model-version-update
• docs-kwargs
• 0.0.4
• 0.0.5
• remove-six
• 0.0.6
• meta-object
• resource-model-update
• plural-refs
• 0.0.7
• service-subresources
• collection-path-fix
• s3-ident-fix
• 0.0.8
• 0.0.9
• model-collision
• 0.0.10
• ref-load
• s3-high-level
• migration-guide
• 0.0.11
• doc-structure
• 0.0.13
• 0.0.14
• 0.0.15
• threading-doc
• 0.0.17
• 0.0.18
• 0.0.19
• 0.0.20
• 0.0.22
• 1.0.0
• 1.0.1
• 1.1.0
• 1.1.2
• 1.1.3

Build # 101

Build Type

push

travis-ci

Committed by danielgtaylor

Commit Message

Fix several name collisions.

This is a workaround to fix a couple of existing issues and hopefully
mitigate future problems with the resource JSON descriptions. It is
only a partial fix and does not update docs, but currently only
two issues exist:

1. `ec2.RouteTable.associations` is defined both as an attribute via its
   shape and via a `hasMany` collection. The collection is renamed to
   `associations_collection`.
2. `ec2.VpcPeeringConnection.vpc` is defined both as an attribute via its
   shape and via a `hasOne` reference. The reference is renamed to
   `vpc_reference`.

Tests have been updated to take this renaming into account, and
a warning is logged each time we rename something, so we can use that
in the future for auditing the resource JSON files.

Run Details

10 of 10 new or added lines in 1 file covered. (100.0%)

548 of 558 relevant lines covered (98.21%)

3.92 hits per line