Add project name to the project deleted notification event

[Todd Johnson]

I have some code that cleans up openstack resources when a project is deleted by listening for the identity.project.deleted notification event. This event payload only includes the project id. It would be nice if it also included the project name. I send an email to the admin with resources that are cleaned up and it would be nicer to have the project name as well as the id. Since the project has already been deleted by the time i receive the event, i can't go back to keystone to get the project name.

[Guang Yee (guang-yee)]

So we had this argument in the past. Quite a few of those in fact, about conveying names in generate, in the notification message payload. As I recall, the counter arguments were

1. names are mutable, and
2. as resources are being deleted, new resources can take on the same name, and
3. the only thing we can guarantee that is globally unique is the resource ID.

I am a proponent of adding name to notification payload. Reasons are

1. a notification is really a snapshot of an event that happened in Keystone, and
2. they will be aggregated by Security Incident and Event Monitoring (SEIM), and
3. as indicated above, operational workflow is depending on it

So I say lets do this.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/320299

[Dolph Mathews (dolph)]

If we're going to make this change, we should *uniformly* include the names of all resources that have names (rather than treat projects as being special): domains, users, roles, groups, etc.

[Lance Bragstad (lbragstad)]

I attempted to capture some of the discussion we had on this topic at the summit in Austin [0].

[0] http://lbragstad.com/improving-auditing-in-keystone/

[OpenStack Infra (hudson-openstack)]

Change abandoned by Steve Martinelli (<email address hidden>) on branch: master
Review: https://review.openstack.org/320299
Reason: no change in 5 months, and lots of overlap with https://review.openstack.org/#/c/288643/, lets use that one instead