I think it has no relate to 'deactivated' status.
Either 'active' or 'deactivated', users can both change the image's size through v1 API.
So maybe the problem is that size can be updated via v1 api. We should reach an agreement that whether we should support it.
In v1, I see that image can be created with size input(only location and copy_from), but size can be changed with every image.
I think it has no relate to 'deactivated' status.
Either 'active' or 'deactivated', users can both change the image's size through v1 API.
So maybe the problem is that size can be updated via v1 api.
We should reach an agreement that whether we should support it.
In v1, I see that image can be created with size input(only location and copy_from), but size can be changed with every image.