client: Unset project when querying permissions.

[markylaing]

lxc permission list expects an explicit project=<project_name> argument. If the client has a project set (other than default) then all requests made by the client will add a project=<project_name> query parameter if it is not already set. This leads to confusing/inconsistent results for this command.

[tomponline]

@markylaing how is this handled already for other scenarios where project param isn't relevant, such as storage pool list?

[tomponline]

@markylaing what i mean is, should the project param be ignored on the server rather than being removed in the client?

[markylaing]

@markylaing what i mean is, should the project param be ignored on the server rather than being removed in the client?

I guess for other APIs the project parameter is ignored. In this case the permissions API accepts two query parameters: project and entity_type. Unlike other APIs, project really is just a filter and not a requirement, so we don't want the client to specify it if it hasn't been specified in the CLI.

[tomponline]

@markylaing what i mean is, should the project param be ignored on the server rather than being removed in the client?

I guess for other APIs the project parameter is ignored. In this case the permissions API accepts two query parameters: project and entity_type. Unlike other APIs, project really is just a filter and not a requirement, so we don't want the client to specify it if it hasn't been specified in the CLI.

I see. Makes sense, so project param should always be specified explicitly on the command flags and not taken from the current active project?

Can you add a comment explaining what you just said there for future readers too please.