airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2876) Django: Application Editor (Module/Interface/Deployments)
Date Mon, 17 Sep 2018 14:24:00 GMT

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

ASF subversion and git services commented on AIRAVATA-2876:
-----------------------------------------------------------

Commit 0ba004e71e87e9c2801b479fc5674d3082a7e8d8 in airavata's branch refs/heads/develop from
[~marcuschristie]
[ https://gitbox.apache.org/repos/asf?p=airavata.git;h=0ba004e ]

AIRAVATA-2876 Delete App Deployment sharing entity when deployment deleted


> Django: Application Editor (Module/Interface/Deployments)
> ---------------------------------------------------------
>
>                 Key: AIRAVATA-2876
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2876
>             Project: Airavata
>          Issue Type: Story
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>
> TODO
> * [ ] Guard against unloading browser page when there are unsaved changes
> * [ ] Only allow admins to edit applications and interfaces (need to guard this on the
backend as well)
> * [x] Use normal sharing rules to control who can edit a deployment
> * [ ] white background for application editor (custom background color based on current
route?)
> * [ ] enum selector component would be generally useful
> * [x] ordered list serializer field that orders output by a numeric field (on read) and
updates that numeric field (on write)
> * [x] CommandObjects editor and SetEnvPaths editor
> * [ ] transitions on input and output fields? (we now have synthetic keys for them)
> * [ ] Do we really need the Vuex store? Maybe just have ApplicationEditorContainer handle
this logic in a simpler way
> * [x] load a list of all application modules instead of only "accessible" modules
> * [x] fix setting id when saving module, interface, etc. (registry-refactoring regression)
> * [ ] delete application
> * [ ] add sharing button to app deployment editor
> * [ ] deployments aren't listed if there is no GroupResourceProfile for that compute
resource. Maybe only allow creating a deployment for compute resources in GroupResourceProfiles?
Or list deployments irrespective of GroupResourceProfile?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message