Why Senlin choose to store auth_url in profile table?

I'm using stable/queens Senlin and notice Senlin stores the keystone auth_url in it's profile table as every time user creates a cluster profile, the auth_url from the context is stored into Senlin db. When user tries to delete the profile, Senlin uses that auth_url from profile table. https://github.com/openstack/senlin/blob/stable/queens/senlin/profiles/base.py#L152-L160

This results in an issue in our environment. We created some profiles earlier and then changed keystone auth_url in our deployment. The profile delete failed as it used the old auth_url from profile table. So my question is why Senlin choose to store the auth_url in its db? Is that should be a run_time data and always get from context? If the auth_url is changed, are the user expected to run manually db update to change the auth_url in profiles table? Thanks