Bug fix for S3 validation
When the S3 model hasn't been updated in any way, first time we try to update the service partially, that raises exceptions as some values are None at that point in db and we don't handle that appropriately
We risk breaking s3 validation
It should be ensured that S3 service starts as desired and we are able to change the fields as we want to even partially. It should also be tried on a system where we don't have s3 configured that partial updates to the service don't raise exceptions.
S3 row can be deleted from db via following command if such a machine is hard to obtain
midclt call datastore.delete 'services.s3' '1'
1 reflects the id of the s3 row. It can be different if it has been manipulated earlier