Actions
Refactor #6306
closedPossible namespace collisions between libraries and proxy modules
Description
The modular smart proxy has modules named after the component being managed, but in the case of both Chef and Puppet, the proxy module filesystem namespace matches that of the Puppet and Chef gems. This is dangerous as it could create conflicts.
$ head modules/puppet/puppet.rb require 'puppet/puppet_plugin' module Proxy::Puppet; end
This is required as "puppet/puppet", and similarly we have things like "puppet/environment". The Puppet code/gem itself is in the same namespace, so we've been very lucky if none of the files we have in modules/*/*.rb match another in one of those projects.
They should probably move into a proxy/ subdirectory to match the namespace of the modules and classes they declare.
Updated by Dominic Cleal over 10 years ago
- Related to Refactor #4866: As a developer I'd like to break up smart-proxy into multiple components added
Updated by Anonymous over 10 years ago
- Status changed from New to Assigned
- Assignee set to Anonymous
Updated by Anonymous over 10 years ago
- Status changed from Assigned to Ready For Testing
Updated by Anonymous over 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 69f6b3e593dee177c5626a6352a87f4b2e35ec2d.
Actions