Suggested by @andrewghobrial

What do you all think of using the hash of endpoint URL to generate cnsi id in cnsi.go instead of a random guid? The benefit of this is that we can generate a link to application in stratos without having to lookup the endpoint guid. Also endpoint guids right now change every time you reinstall stratos or delete endpiont..

This seems like a really good idea and opens up a whole world of bookmark possibilities.
In terms of the frontend I think we're pretty agnostic to whatever the id is, however it should remain a string and some param names contain guid (not a deal breaker).
@irfanhabib Is there anything backend wise that changing this format might bring up?
Also, wondering if there's anywhere in v2 where we exploit same url endpoints (think in v1 we did something for e2e tests).