Task #5019 (closed)
Opened 8 years ago
Closed 7 years ago
RapidService: User script management
| Reported by: | dzmacdonald | Owned by: | dzmacdonald |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | General | Version: | n.a. |
| Keywords: | n.a. | Cc: | jos@…, jamoore, jburel, jrswedlow |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 0.0d |
| Sprint: | n.a. |
Description
The current method for uploading script and running them using the rapidservice is a little clunky.
The user can upload a script that specifies the username and password for the cluster, and the parameters for the script. This means that the user should be the only person to beable to deploy a script like this.
If the script has no parameters supplied then any user should be able to pass the cluster username and password combination.
There needs to be more thought on this strategy.
Change History (3)
comment:1 Changed 8 years ago by jburel
- Sprint changed from 2011-04-21 (10) to 2011-05-05 (11)
comment:2 Changed 8 years ago by dzmacdonald
- Milestone changed from OMERO-Beta4.3 to Unscheduled
- Sprint 2011-05-05 (11) deleted
comment:3 Changed 7 years ago by jburel
- Remaining Time changed from 1 to 0
- Resolution set to invalid
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Moved from sprint 2011-04-21 (10)