On Mon, Dec 24, 2012 at 10:09 PM, Rohit Yadav <[email protected]> wrote: > Hi Alex, > > We got rid of IdentityMapper and enforced the translation of over the wire > UUID string to internal long int ID, so we know if internal IDs are used in > any case starting 4.1 it will break any client, script that are based off > internal ID and not UUID strings. Few folks on the ML have expressed > concerns, but we need this change and to enforce that we won't have any > backward compatibility for over the wire api params to accept internal IDs. >
I read this, and am left more confused than before. There have been assurances regarding the refactor that no API changes have occurred, but the above seems to contradict that. I'll apologize for being daft (and for not going in and looking at the changes) but can you tell me: 1. what the changes to the API are? 2. Why 'we need this change'? Breaking backward compatibility is a huge deal IMO. Even changes that technically didn't break compatibility but were different than folks expectations (when we introduced UUID) earned us much wailing and gnashing of teeth. Breaking other people's external tools that interact with CloudStack is something that shouldn't be done without much deliberation.
