Alternatively, and perhaps even preferably (team, feel free to weigh in on this), we could alter the API for apply_async_with_reservation to accept both a resource_type and a resource_id, and it can be the thing that concatenates the two (perhaps with a colon or something as a separator) into the actual reservation id. That might be a little cleaner for the callers, so this would be my personal preference.