On Jan 21, 2019, at 1:55 PM, Lance Bragstad <lbragstad at gmail.com> wrote: > > Are you referring to the system scope approach detailed on line 38, here [0]? Yes. > I might be misunderstanding something, but I didn't think keystone was going to iterate all available services and call clean-up APIs. I think it was just that services would be able to expose an endpoint that cleans up resources without a project scoped token (e.g., it would be system scoped [1]). > > [0] https://etherpad.openstack.org/p/community-goal-project-deletion > [1] https://docs.openstack.org/keystone/latest/admin/tokens-overview.html#system-scoped-tokens It is more likely that I’m misunderstanding. Reading that etherpad, it appeared that it was indeed the goal to have project deletion in Keystone cascade to all the services, but I guess I missed line 19. So if it isn’t Keystone calling this API on all the services, what would be the appropriate actor? -- Ed Leafe