Move entity package back to shared

[markylaing]

This PR reverts b463884 and adds a follow up commit to fix imports that have been added after that commit.

We do need to have the entity package in shared so that when adding permissions to groups we can parse the input and create a standardised URL. If the client is very out of date with the server, the worst that might happen is the server will respond to say it doesn't recognise the URL or the entity type. If this is not sufficient, perhaps we can add entity types and entitlements to the metadata API and validate client side that way first.

[tomponline]

We do need to have the entity package in shared so that when adding permissions to groups we can parse the input and create a standardised URL. If the client is very out of date with the server, the worst that might happen is the server will respond to say it doesn't recognise the URL or the entity type. If this is not sufficient, perhaps we can add entity types and entitlements to the metadata API and validate client side that way first.

This seems OK.

Please could you give me an example of where it would be needed to a construct a URL from input?

[markylaing]

Please could you give me an example of where it would be needed to a construct a URL from input?

When adding permissions to a group we have:

lxc auth group permission add <entity_type> [<entity_name>] <entitlement> [<key>=<value>]

Say we have:

lxc auth group permission add storage_volume vol1 can_manage_snapshots project=my-project type=custom pool=default

We need to construct the /1.0/storage/default/volumes/custom/vol1?project=my-project URL. This is added to the api.Permission as a string in the EntityReference field. The server will parse that URL and get an ID for it to be used in the permissions table.

[tomponline]

Thanks!