It's true that the patch doesn't solve in case of creating the resource fails after setting the resource_id. Umm.
I think, we should add new column that refer to previous stack (or resource) for solving this problem fundamentally.
It looks like currently DB doesn't refer previous stack/resource.
It's true that the patch doesn't solve in case of creating the resource fails after setting the resource_id. Umm.
I think, we should add new column that refer to previous stack (or resource) for solving this problem fundamentally.
It looks like currently DB doesn't refer previous stack/resource.