Sorry i should have been more specific. The name changes need to be consumer facing. So if they used to use "FunctionFoo" they would now see "FunctionBar".
Right now i'm thinking via permissions i would hide the legacy ones and create new ones and the legacy ones would use your suggestion.
It would be great if the function itself could define it's own name like how there is a FunctionDescription. Even better would be if i could specify how it's shown to the user..something like Attribute Routing (http://www.asp.net/web-api/overview/web-api-routing-and-actions/attribute-routing-in-web-api-2) so I could specify the directory structure and naming.
Right now i'm thinking via permissions i would hide the legacy ones and create new ones and the legacy ones would use your suggestion.
It would be great if the function itself could define it's own name like how there is a FunctionDescription. Even better would be if i could specify how it's shown to the user..something like Attribute Routing (http://www.asp.net/web-api/overview/web-api-routing-and-actions/attribute-routing-in-web-api-2) so I could specify the directory structure and naming.