Break Backward Compatibility

[josephholsten]

From edelight/chef-mongodb#308

Note: this ticket may be out of date.

Someday soon we're going to have to break backwards compatibility, and we may as well rip the bandage off. This is a tracking ticket for all the backwards incompatible changes that should go into the next breaking release (1.0?).

• allow arbitrary shard names
• separate shard and replicaset names
• remove references to 10gen
• support compound sharding keys
• stop creating a mongodb_instance in mongodb::default
• update default paths to match mongodb defaults
• use yaml format config, incompatible with < 2.6 mongo

[shortdudey123]

Moved from 1.1.0 to 1.0.0 since i cover most of this already in the rewrite

[shortdudey123]

Completed in v1 rewrite

• remove references to 10gen
• update default paths to match mongodb defaults
• use yaml format config, incompatible with < 2.6 mongo

Todo

• stop creating a mongodb_instance in mongodb::default
• support compound sharding keys
• allow arbitrary shard names
• separate shard and replicaset names

[shortdudey123]

• [breaking change] Stop creating a mongodb_instance in mongodb::default #75 => stop creating a mongodb_instance in mongodb::default
• support compound sharding keys #142 => support compound sharding keys
• allow arbitrary shard names #141 => allow arbitrary shard names
• separate shard and replicaset names #143 => separate shard and replicaset names

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.