No way to discover one's own appID

[Michael Terry]

In Touch land, we have a concept of an appID, which is formatted something like PKG_CMD_VER (or in snappy I think you use a profile ID along the lines of snap.PKG.CMD).

The package name is provided as SNAP_NAME. And the version is provided as SNAP_REVISION.

But nothing provides the current application/command name. Applications themselves may know this implicitly, but libraries that want to use the current appID need some way to determine it.

So either an environment variable like SNAP_APP (or SNAP_COMMAND) or SNAP_ID for the full thing would be useful.

[Jamie Strandboge (jdstrand)]

For context, as mentioned the appID in Touch was <pkgname>.<appname>.<revision>. The concept of appID lives on in snappy as snap.$SNAP.<command>. If the goal is to construct anything yourself, the new env var probably shouldn't be SNAP_APP or SNAP_COMMAND since both imply (to me anyway) '<command>' or '$SNAP.<command>'.

[Zygmunt Krynicki (zyga)]

Can you please clarify what is the intended use case of "appID". Internally we have the so-called security-tag, which looks like snap.foo.bar. It would be easy for us to convey the new "id" but please explain how this would be useful for you in practice.