[jira] [Created] (AIRAVATA-3623) airavata-django-portal-sdk: handle case that storage_resource_id isn't configured in USER_STORAGES

["Marcus Christie (Jira)" <ji...@apache.org>]

Marcus Christie created AIRAVATA-3623:
-----------------------------------------

             Summary: airavata-django-portal-sdk: handle case that storage_resource_id isn't configured in USER_STORAGES
                 Key: AIRAVATA-3623
                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3623
             Project: Airavata
          Issue Type: Bug
          Components: Django Portal
            Reporter: Marcus Christie
            Assignee: Marcus Christie


A data product created on an alternate deployment of a gateway will have a different storage_resource_id and the other deployment of the gateway won't be able to resolve it. That's fine, but it shouldn't assume that the storage_resource_id will always be found in USER_STORAGES.

see for example, exists() https://github.com/apache/airavata-django-portal-sdk/blob/master/airavata_django_portal_sdk/user_storage/api.py#L281

if storage_resource_id isn't found, then module_class_name is {{None}}: https://github.com/apache/airavata-django-portal-sdk/blob/master/airavata_django_portal_sdk/user_storage/api.py#L62-L65

Which results in a {{'NoneType' object has no attribute 'rsplit'}} error.




--
This message was sent by Atlassian Jira
(v8.20.7#820007)