Make parameter naming consistent about service-fabric-cli

[mani-ramaswamy]

This should also be done in a backwards compatible manner, so if "fabric:/" is specified, we still accept it if that's the convention chosen. Or if the convention is not to specify "fabric:/", the CLI automatically removes it if the customer specifies it.

[echen805]

@samedder, is it okay if I take this up? It looks like there's inconsistency between sfctl.custom_app.create and sfctl.custom_app.upgrade but thats the only one I've encountered

[Christina-Kang]

@echen805 for sure! We would very much appreciate it! :)

[echen805]

Great! So it looks like the functions that require application_id, do not want "fabric:/" in their value since the function automatically adds it at the beginning.

I looked through the contribution wiki and I did not see any ideas of which way I should go with this. Should I change parameter to application_name so future users will use a value with "fabric:/" in front? And make it backwards compatible so users who are currently using application_id will not be affected.

[echen805]

Hi @Christina-Kang, is it okay if I still work on this?