[jira] [Commented] (AIRAVATA-3435) INVESTIGATE: When Application name changes, the STDOUT and STDERR file names doesn't get updated with the latest name

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

    [ https://issues.apache.org/jira/browse/AIRAVATA-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318027#comment-17318027 ] 

Marcus Christie commented on AIRAVATA-3435:
-------------------------------------------

[~eroma_a] I don't think the STDOUT or STDERR outputs are named based on the application name. They just are given static "Standard-Out" and "Standard-Error" names https://github.com/apache/airavata-django-portal/blob/develop/django_airavata/apps/api/static/django_airavata_api/js/models/ApplicationInterfaceDefinition.js#L48. But correct me if I'm wrong.

> INVESTIGATE: When Application name changes, the STDOUT and STDERR file names doesn't get updated with the latest name
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-3435
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3435
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: Django Portal
>    Affects Versions: 0.18
>         Environment: https://django.seagrid.org/
>            Reporter: Eroma
>            Assignee: Marcus Christie
>            Priority: Major
>             Fix For: 0.19
>
>
> # Create a new application with module, interface and deployment.
>  # The application STDOUT and STDERR are created with the application name.
>  # Change the application name only
>  # The STDOUT and STDERR names are not updated with the new application name.
>  # An simple save in the interface, will updated the names at the moment but if user only changes the Description tab name, the STDOUT and STDERR remains with the old name.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)