{"push_id":2944817109,"size":1,"distinct_size":1,"ref":"refs/heads/tickets/master/MODULES-5493-cannot-manage-two-same-name-applications","head":"fa732ac11df736347ba084c8cae7b23f30555e35","before":"bf05758164c54260c4f7a3a965d9981ea4d7cb27","commits":[{"sha":"fa732ac11df736347ba084c8cae7b23f30555e35","author":{"name":"Bill Hurt","email":"fa132489e5ac82b80336cbdb52926cc5bb43f8cf@gmail.com"},"message":"(MODULES-5493) Manage Two Same Name Appications\n\nThis commit fixes a bug in the this module uses the composite name key\nfeature. Prior to this change the `sitename` property was specified as\na part of the composite key. Unfortunately, properties are not valid\ncomponents of a compsite key and the directive was ignored. This meant\nthat in truth there was only attribute considered for the naming key,\nand thus for uniqueness, which was the `applicationname` parameter.\n\nThis commit changes the `sitename` property to a paremeter to ensure\nthat it is considered a part of the composite key. Now if you have two\nsites that need an application with the same name on a single instance\nof IIS, you can do that.","distinct":true,"url":"https://api.github.com/repos/RandomNoun7/puppetlabs-iis/commits/fa732ac11df736347ba084c8cae7b23f30555e35"}]}
{"actor":{"display_login":"RandomNoun7"}}