airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AIRAVATA-2876) Django: Application Editor (Module/Interface/Deployments)
Date Fri, 21 Sep 2018 18:59:00 GMT


ASF subversion and git services commented on AIRAVATA-2876:

Commit 3c86d7b214a3fd9f1b6b3bb672b6ec30ccb50b3e in airavata-django-portal's branch refs/heads/master
from [~marcuschristie]
[;h=3c86d7b ]

AIRAVATA-2876 Remove Vuex store, load all modules in dashboard

> Django: Application Editor (Module/Interface/Deployments)
> ---------------------------------------------------------
>                 Key: AIRAVATA-2876
>                 URL:
>             Project: Airavata
>          Issue Type: Story
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
> * [x] Guard against unloading browser page when there are unsaved changes
> * [x] 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
> * [ ] 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)
> * [x] 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)
> * [x] delete application
> * [x] add sharing button to app deployment editor
> * [x] 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

View raw message