The "new" behavior in DCOS is that the frontend does NOT uninstall service which were installed from the universe `dcos package install xyz`. The logic being that the dcos package uninstall may be necessary for the uninstall hook. Additionally the ability to see from the UI what is installed (those you can uninstall it has been removed).
When trying to remove from the service UI a service which was installed from the catalog a dialog box prompts the need to use the CLI. That prompt is a `dcos package uninstall ` command. This behavior is driven off seeing certain flags in the app definition.
Here is the issue. IF I decided I wanted to use the admin router for an application that I didn't have defined in the universe by using the DCOS_SERVICE_NAME. There is nothing stopping me from doing that in the UI at the time of launch... however if I try to remove the app, the UI will not let me and it provides instructions on `dcos package uninstall `... however if I try to uninstall it the CLI complains that this isn't a service and does not uninstall it.
Since many DCOS catalog services do NOT have an uninstall behavior... it would be IMO better to introduce a new LABEL that introduces this new behavior. DCOS_UNINSTALL_HOOK = true or something. Then require all services which require this behavior to have this label.
Or have the remove service do the uninstall... or have the dcos package uninstall remove services as well which were not in the universe.
Here is a sample app: